1. No category

l
How-to Guide
SAP NetWeaver ‘04
SAP NetWeaver 2004s
How To…
Resolve Visual
Composer
Issues
DOCUMENT VERSION 2.0 – April 2006
Applicable Releases:
SAP Visual Composer 6.0, 7.0
SAP Netweaver ‘04
SAP Netweaver 2004s
© Copyright 2005 SAP AG. All rights reserved.
No part of this publication may be reproduced or
transmitted in any form or for any purpose without the
express permission of SAP AG. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its
distributors contain proprietary software components of
other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent
Miner, WebSphere, Netfinity, Tivoli, and Informix are
trademarks or registered trademarks of IBM Corporation
in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered
trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame,
WinFrame, VideoFrame, and MultiWin are trademarks
or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
®
registered trademarks of W3C , World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other
SAP products and services mentioned herein as well as
their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and
service names mentioned are the trademarks of their
respective companies. Data
contained in this document serves informational
purposes only. National product specifications may vary.
These materials are subject to change without notice.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes
only, without representation or warranty of any
kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only
warranties for SAP Group products and services are those
that are set forth in the express warranty statements
accompanying such products and services, if any.
Nothing herein should be construed as constituting an
additional warranty.
These materials are provided “as is” without a warranty
of any kind, either express or implied, including but not
limited to, the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or
consequential damages that may result from the use of
these materials.
SAP does not warrant the accuracy or completeness of
the information, text, graphics, links or other items
contained within these materials. SAP has no control
over the information that you may access through the
use of hot links contained in these materials and does not
endorse your use of third party web pages nor provide
any warranty whatsoever relating to third party web
pages.
SAP NetWeaver “How-to” Guides are intended to
simplify the product implementation. While specific
product features and procedures typically are explained
in a practical business context, it is not implied that those
features and procedures are the only approach in solving
a specific business problem using SAP NetWeaver. Should
you wish to receive additional information, clarification
or support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”)
included in this documentation are only examples and
are not intended to be used in a productive system
environment. The Code is only intended better explain
and visualize the syntax and phrasing rules of certain
coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall
not be liable for errors or damages caused by the usage of
the Code, except if such damages were caused by SAP
intentionally or grossly negligent.
1 Scenario
When using Visual Composer, you may run into BI problems, Portal problems, or Visual
Composer problems. This paper shows how to identify the true source of problems and
lists common issues and resolutions.
2 Identify the Problem
2.1
Is it a BI Problem? (Visual Composer 6.0 only)
1. Go to transaction WSADMIN
2. Define J2EE Server.
3. Enter the URL for the J2EE Server if
it isn’t already there and hit Save.
4. Browse to “SOAP Application for
RFC-Compliant FMs ->
query_view_data -> Data for the
query view” and hit Run.
5. Choose “Document Style” and hit
the Green Check.
6. Login with your username and
password and hit Submit.
7. Hit Test.
8. Run the “GetQueryViewData”
operation.
9. Specify an Infoprovider and Query
and choose “Skip” for ViewId and
Parameter. Hit Send.
10. Make sure a successful response is
returned. If this is successful, BW is
configured properly. If this is not
configured properly, go to the
section on troubleshooting BW
Issues.
3 Troubleshooting BW Issues
3.1
“Authority Check” error
-
Ensure that your BW User ID has the following authorizations:
o Auth Object S_SERVICE
-
Ensure that your BW User ID has S_RS_COMP values for the InfoCube
and Query in Question.
-
Ensure that your BW User ID has the S_DEVELOP values specified
below.
3.2
“Virtual Interface not found” error
This error will give you a message such as:
"Error 32010: Cannot execute query. No result returned or XML returned
in the result contains an error. Virtual Interface not found."
1. Go to transaction SE80 and choose
“Edit Object”
2. Choose the “Enterprise Services”
tab and specify the Virtual Interface
“query_view_data” and hit the Green
Check.
3. Hit the “Activate” button to
regenerate your Virtual Interface.
3.3
“Serialisation” error
1. Go to transaction SICF and choose
“External Aliases”.
2. Delete and recreate the external
alias
“/default_host/sap/bc/srt/rfc/sap/quer
y_view_data”.
3. Go to transaction SE80 and choose
“Edit Object”.
4. Choose “Enterprise Services” and
specify the Web Service Definition
“QUERY_VIEW_DATA”. Hit the
Green Check.
5. Click on the “Properties” Tab.
Double click on the
“query_view_data” Virtual Interface
to open the Virtual Interface.
6. Click on the “Properties” tab.
7. Double Click on the
“RRW3_GET_QUERY_VIEW_DATA
” function module.
8. Active this function Module. The hit
back.
9. Activate the “Virtual interface” and
hit back.
10. Activate the web service definition.
4 Installing and Configuring BI Java Connectors
4.1
BI JDBC Connector to SQL Server
1. Login to the Visual Administrator:
go.bat
2. Make sure the JDBC drivers have
been acquired from the software
vendor and installed on the server. If
the JDBC driver was not set up, it
can be added by clicking on the
“Create Driver” button the cursor is
over in the diagram to the left and
entering a name for the driver.
3. Add the jar files to the driver entry
and Click OK.
4. The new driver will then appear. We
have now added a driver to be used
in our BI Connector.
5. Verify the BI JDBC Connector
Resource Adapter exists. We can
see that the BI JDBC Connector is
active and running with the defaults
set.
6. To create a new connector, select
the Connector SDK_JDBC and click
the Clone button to create a new BI
JDBC Connector and enter a name
for the connector.
7. Select the recently created
Connector and choose the Resource
Adapter tab. Click the Add button to
associate additional Resources with
the Connector
8. To add resources, enter the name of
a Resource we wish to associate
with the Connector.
9. Login to the Portal.
10. Create a New System on the Portal.
Go to “System Administration ->
System Configuration” and click on a
folder. Then create a System by
choosing “New from Par -> System”.
11. To create a BI JDBC System within
the Portal, select the
“com.sap.portal.systems.BIUDI”
PAR and choose Next.
12. Select the “SAP_BI_JDBC” option
and choose Next.
13. Enter a System Name, ID and Prefix
and choose Next. Then Choose
Finish and Open the Object for
Editing.
14. Navigate to the Connection
properties option in the Property
Category dropdown list. Enter in the
database connection URL, do not
forget to specify the DatabaseName
you wish to connect to in the URL
string. Enter in the Driver Class
name.
15. Navigate to the User Management
Property Category and choose the
admin,user option.
16. Verify the ConnectionFactory
created in step 1 “MSSQL_JDBC” is
specified under the “Show All”
Property Category.
17. From the Display dropdown list
choose the System Aliases option.
Enter an alias for the system and
choose the add button. Don’t forget
to save.
18. To create user mapping, Navigate to
the User Administration -> User
Mapping tab and enter your
username and choose Start.
19. Once you have found your user
choose the Edit button. Choose the
BI JDBC System created. Enter user
and password information for this
system and save your settings.
20. To test the connection, navigate
back to the System Configuration
area. Choose the BI JDBC System
you created. Navigate to the
Connection Tests area and choose
the Test Button. This should be
successful.
4.2
BI JDBC Connector to Oracle
Located at:
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
Driver: oracle.jdbc.driver.OracleDriver
URL: jdbc:oracle:<drivertype>:@<database>
jdbc:oracle:thin:@myhost:1521:orcl
4.3
BI JDBC Connector to MaxDB
Driver: com.sap.dbtech.jdbc.DriverSapDB
URL: jdbc:sapdb://<server>/<database>
e.g. jdbc:sapdb://ilgm76/mydb
4.4
BI JDBC Connector to CSV using Relique Driver
Driver: org.relique.jdbc.csv.CsvDriver
URL: jdbc:relique:csv:c:\\csv
4.5
BI SAP Query Connector
1. To verify that you have created an
infoset with available data, login to
your backend system. Navigate to
transaction sq02. Identify the InfoSet
which you will configure your
DataService on top of. Verify there is
data within the InfoSet.
2. Login to the portal. Create a New
System from PAR
3. Choose the
“com.sap.portal.systems.BIUDI”
PAR.
4. Choose the “SAP_BI_SAPQuery”
System type.
5. Give the system a name, ID and
system prefix and Open the Object
for editing.
6. Navigate to the Connection
Properties Category. Enter the
appropriate information for the
location of the Application Server,
the Message Server, Client and
System Number. The Query Area
entry determines where you access
data from
X = Global Area (Cross-client)
‘ ‘ = Standard Area (Client–specific)
Save your information.
7. Under the ‘Info’ Property Category
enter a Description and System
Name and choose Save.
8. Navigate to the ‘UserManagement’
Property Category and specify the
User Mapping Type (e.g.
admin,user) and Save your
information.
9. Within the System Alias Editor
create a System Alias. Save your
information.
10. To configure the user mapping to the
backend system, Navigate to the
User Administration -> User
Mapping tab and enter your
username and choose Start.
11. Once you have found your user
choose the Edit button. Choose the
BI SAPQ System created. Enter
user and password information for
this system. Save your settings.
12. To test the connection, Navigate
back to the System Config area.
Choose the BI SAPQ System
created. Navigate to the Connection
Tests area. Choose the Test Button.
4.6
BI ODBO Connector
1. Verify you have ODBO system to
connect to. Connect to your
Microsoft Analysis Service running
on your SQL Server. Identify your
Catalog you will connect to. Identify
a cube which you want to use to
retrieve data from.
2. A good trick to figure out your
connection string to your ODBO
system is to create a udl (universal
data link) file.
3. You can do this by creating a new
text file and giving it the .UDL suffix.
4. From here you can specify your
connection properties and test your
connectivity to Microsoft Analysis
Services (or SAP Netweaver BI)
5. After configuring this UDL file and
testing the connection successfully
you can send the file to notepad to
read the embedded connection
string.
6. You now have a connection string
for the ODBO Connector you are
about to create.
7. Login to the portal and Create a New
System from PAR
8. Choose the BIUDI PAR
9. Choose the SAP_BI_ODBO System
type
10. Give the system a name, ID and
system prefix and Open the Object
for editing.
11. Navigate to the Connection
Properties Category. Enter the
connection string we created in step
1. Save your information.
12. Navigate to the User Management
tab, set up the User Mapping Type.
Save your information.
13. Create a system alias from the
System Alias Editor.
14. Navigate to the User Administration > User Mapping tab. Enter your
username and choose Start.
15. Once you have found your user
choose the Edit button. Choose the
BI ODBO System created. Enter
user and password information for
this system. Save your settings.
16. Navigate back to the System Config
area. Choose the BI ODBO System
created. Navigate to the Connection
Tests area. Choose the Test Button.
4.7
BI XMLA Connector
1. Login to the SAP BW system you
will connect to.
2. Go to transaction “SICF”.
3. Test the XMLA Service
4. Login to the SAP Web AS
5. Verify that the test succeeded! The
XMLA Service on the SAP
NetWeaver Web Application Server
is running, we can now create a BI
XMLA System.
6. Navigate to transaction SMICM –
The ICM Monitor
7. Select the service HTTP or HTTPS
you will use to connect to the Web
Server. Display the Service.
8. Concatenate the Protocol Host
name and port to create the 1st part
of our URL (ie
http://iwdf9484.wdf.sap.corp:54080)
9. Navigate to transaction SICF – The
Internet Connection Framework
10. Find your way to the XMLA service
once again. Display the Service. The
path to the service is listed here.
Concatenate the string after
/default_host/ to the end of the URL
we have built. Add XMLA on to the
end of the URL to access the ICF
object / XMLA Service (ie
http://iwdf9484.wdf.sap.corp:54080/s
ap/bw/xml/soap/xmla)
11. Login to the portal. Create a New
System from PAR
12. Choose the BIUDI PAR
13. Choose the SAP_BI_XMLA System
type
14. Give the system a name, ID and
system prefix and Open the Object
for editing.
15. Navigate to the Connection
Properties Category. Enter the URL
we built in step 2. Save your
information.
16. Navigate to the User Management
tab, set up the User Mapping Type.
Save your information.
17. Create a system alias within the
System Alias Editor. Make sure you
Save.
18. Navigate to the User Administration > User Mapping tab. Enter your
username and choose Start.
19. Once you have found your user
choose the Edit button. Choose the
BI XMLA System created. Enter user
and password information for this
system. Save your settings.
20. Navigate back to the System Config
area. Choose the BI XMLA System
created. Navigate to the Connection
Tests area. Choose the Test Button.
5 Configuring SAP BW Native Connections
5.1
Configuring SAP BW Connections
For Visual Composer 6.0, ensure that your support pack is SAP BW 3.5 SP3 or
higher. For Visual Composer 7.0, ensure your support pack is SAP BW 3.5 SP14
or higher and Enterprise Portal is 6.0 SP14 or higher.
1. Navigate to transaction SMICM –
The ICM Monitor
2. Select the service Protocol HTTP or
HTTPS you will use to connect to
the SAP Web Application Server.
Display the Service
3. Login to the portal. Create a New
System.
4. Choose the SAP System using
dedicated application server System
type.
5. Give the system a name, ID and
system prefix. Open the Object for
editing.
6. Navigate to the Web Application
Server Property Category. Enter the
WAS Description, Host Name, Path
and Protocol which we determined in
step 1.
7. Navigate to the User Management
tab, set up the User Mapping Type.
Save your information.
8. Navigate to the Connector Property
Category. Enter the Application host
(this was determined this in step 1).
Enter the Gateway Host (generally
the Application Host). Enter the
Gateway Service (Concatenation of
SAPGW and System Number).
Enter the Logical System Name,
Client, System ID and System
Number.
9. The System Type must be set to
SAP_BW. Save the information.
10. Create a system alias within the
System Alias Editor
11. Navigate to the User Administration > User Mapping tab. Enter your
username and choose Start.
12. Once you have found your user
choose the Edit button. Choose the
SAP R3 Dedicated Server System of
type SAP_BW created. Enter user
and password information for this
system. Save your settings.
13. Navigate back to the System Config
area. Choose the SAP R3 Dedicated
Server System created. Navigate to
the Connection Tests area. Select
the SAP Web AS Connection and
the Connection Test for Connectors
Tests. Execute the Test. You are
now ready to use this system.
6 Troubleshooting Enterprise Portal Issues
6.1
General Issues
- Ensure that you’ve created a unique system alias. You cannot have 2
different connections with the same system alias.
- Check User Mapping – SSO or UIDPW?
6.2
Check Secure Store
1. Login to the Portal and navigate to
System Administration -> System
Configuration -> UM Configuration > Direct Editing
2. Check your secure store setting and
ensure that it mirrors your encryption
type (strong or weak).
6.3
Do not use “localhost” in a URL!
- Ensure that a fully qualified domain name or an IP address is used to test
the connection between the Portal and the Visual Composer Server. Make
sure you can “ping” both servers from each other.
6.4
Cannot login to the Portal from Visual Composer (VC 6.0 only)?
When trying to log to portal from visual composer, either a blank blue screen or
recurring login screens are returned without the login succeeding.
3. Login to the Portal and navigate to
System Administration -> System
Configuration -> UM Configuration > Direct Editing
4. Change login.ticket_include_cert=1
to login.ticket_include_cert=0. If this
isn’t included in the file, then add
entry login.ticket_include_cert=0.
Afterwards, restart the J2EE.
login.ticket_include_cert=1 is a
deprecated function. It saves the
certificate in the logon ticket, and in
some cases this ticket is too big to
set it as cookie and can’t logon.
If you still have problems, this may be a problem with permissions.
1. Start the Visual Administrator.
2. Go to Server -> Services -> Security
Provider
3. Choose the “Security Roles” tab.
4. Choose component “SAP-J2EEEngine”.
5. Choose the “administrators” role and
choose the “Add” under Users.
6. Specify “J2EE_ADMIN” and hit
Search. Choose “J2EE_ADMIN” and
hit OK.
7. Make sure the “J2EE_ADMIN” user
exists under Users.
8. Choose KeyStoreViewCreator and
make sure the user “J2EE_ADMIN”
is added to that role as well.
6.5
Is it a JCO error?
Check if the problem is in JCO level, perform JRfcTest as described in note
598891.
6.6
Systems List is Missing in Visual Composer
With this error, you cannot get a dropdown list of systems in Visual Composer.
You may even get the following error message:
"Bad or missing XML Object"
In many cases, this is due to UME issues. Check the logs to see if Visual
Composer tries to login to the Portal using the user “Guest”. This would fail
because “Guest” isn’t an authorized user in the Portal. To check the logs, see the
sections in this document on configuring and viewing the logs. If it is a UME
issue, follow these steps to solve this issue. You can see this in the
defaultTrace.trc file.
1. Start the Visual Administrator.
2. Go to Server -> Services -> Security
Provider
3. Under “components”, choose
“ticket”.
4. In change mode, choose
“com.sap.core.server.jaas.EvaluateT
icketLoginModule” and choose
“Modify”.
5. Make sure the flag is set as
“SUFFICIENT” and you have
“ume.configuration.active=true” set.
Hit OK. For details on UME
configuration, see
http://help.sap.com/saphelp_nw04/h
elpdata/en/cb/ac3d41a5a9ef23e100
00000a155106/content.htm
6.7
Cannot Retrieve InfoAreas error
"Error -32002: Cannot retrieve infoareas.
Service not found:
com.sap.portal.guimachine.BIKit.CommandHan....."
Make sure you deploy BIMMR sca and then BIUDI sca. The order is important.
7 Troubleshooting Visual Composer 6.0 Issues
7.1
XML Parser Issues
-
Ensure Microsoft XML Parser SP2 is installed on the Visual Composer
Server, the Enterprise Portal Server, and the client machine.
7.2
Cannot See Anything within the Visual Composer Storyboard?
7.3
Ensure that the Adobe SVG Viewer is installed on the client machine.
No Visual Composer was found at specified address
"Fatal Error : No Visual composer was found at specified address
Error reading server parameters in url:bin/gm1433030.asp"
This is because the file “~server.ini” is not accessible by the program. Make sure
the ~server.ini file is accessible by the browser by trying
http://<server name>/VCServer/~server.ini.
If you still encounter problems, see OSS Note 817495.
7.4
Using Fully Qualified Domain Name to start Visual Composer
When accessing Visual Composer using the full domain name, an "Access
Denied" error is raised in the browser (Javascript Error). Visual Composer is not
loaded
Current available workaround: Add the domain name to the trusted sites in the
browser's settings.
1. Go to Tools -> Internet Options ... -> Security -> Trusted Sites.
2. Click on Sites...
3. Add the full domain name (when accessing VC) to the list of sites.
If you still encounter problems, see OSS Note 875938.
7.5
Ensure Visual Composer 6.0 patch 6 is installed correctly
-
Make sure you make the registry settings for Windows Server 2003.
7.6
Ensure the the VCRole is assigned on the Portal (VC 7.0 only)
-
7.7
Ensure that the Portal UserId has the VCRole assigned.
Flash compilation error:
If you get this error:
Error in executing a process for Flex compilation, Warning: Missing
charsets in String to FontSet conversion
Warning: Cannot convert string "-dt-interface system-medium-r-normal-s**-*-*-*-*-*-*-*" to type FontSet
Warning: Cannot convert string "-monotype-arial-regular-r-normal *-140*-*-p-*-iso8859-1" to type FontStruct
Warning: Missing charsets in String to FontSet conversion
Warning: Cannot convert string "-dt-interface user-medium-r-normal-s*-**-*-*-*-*-*-*" to type FontSet
Or this error:
Error in executing a process for Flex compilation,
java.lang.InternalError: Can't connect to X11 window server using ':0.0'
as the value of the DISPLAY variable.
This is most likely because the server doesn't have a graphical subsystem (i.e. a
graphics card and monitor). The Flex server uses Java's AWT (Abstract Window
Toolkit) to implement compile time image embedding and SVG. By default, the
Java Virtual Machine tries to use the hardware-based graphical capabilities of the
machine to implement AWT. For servers without a graphical interface, the above
error will be thrown.
Follow the following steps from note 886209:
1. Open the following file:
j2ee\cluster\server0\apps\sap.com\irj
\servlet_jsp\irj\root\portalapps\com.s
ap.vc.mmcompiler\res\root\WEBINF\flex\flex-config.xml”
2. In the <compiler> element, find the
<headless-server> parameter, and
change it's value to true. Around line
#146, change <headlessserver>false</headless-server> to
<headless-server>true</headlessserver>
8 Still Have Problems?
8.1
How to Turn on Logs for Visual Composer 6.0
3. Open up the “~server.ini” file in the
IIS Server directory. If your root is
“C:\Intepub\wwwroot\”, then the file
is located at
“C:\Inetpub\wwwroot\SAP
NetWeaver Visual
Composer\server\~server.ini”.
4. Change the LogLevel to “0”. The
default value is “2”. Save this file.
5. Start the Visual Administrator.
6. Go to “server -> services -> Log
configurator”
7. See the matrix within this document
on the specific errors and logs to
turn on. Make sure you turn the log
severity to “All” for the component
you are having issues with.
8.2
How to Turn on Logs for Visual Composer 7.0
1. Start the Visual Administrator.
2. Go to “server -> services -> Log
configurator”
3. Go to the “Locations” tab.
4. Go to com -> sap -> portal ->
connectors and turn up the severity
to “All” for connection issues.
5. Go to com -> sap -> portal -> vc and
turn up the log severity to “All” for
any runtime, designtime, or HTMLB
issues.
6. Go to com -> sap -> portal -> uddi
for any issues with soap service and
turn up the logging severity to “All”.
7. For general Visual Composer
issues, go to com -> sap -> portal ->
visualcomposer and turn up the
logging severity to “All”.
8. For any other issues, including UME,
and SSO, see the log matrix to see
which logs to turn on.
8.3
Log Component Matrix
If you don’t see your systems list in VC 6.0 or you’re having connection problems,
set the logs for the following components.
com.sap.portal.connectors -> set severity to ALL.
com.sap.portal.connectors.R3 -> -> set severity to ALL.
com.sap.portal.JCOCLientPool -> set severity to ALL
If you have UME Issues,
com.sap.engine.services.security -> set severity to ALL.
com.sap.security.core.server.jaas -> set severity to ALL.
com.sap.security.core.ticket -> set severity to ALL.
com.sap.security.core.util -> set severity to ALL.
com.sap.security.core.persistence -> set severity to ALL.
For Visual Composer 7.0, if you are having issues with seeing your systems list, set the logs for
the following components:
com.sap.portal.connectors -> set severity to ALL.
com.sap.portal.connectors.R3 -> -> set severity to ALL.
com.sap.mw -> set severity to ALL (This is for jco issues)
This entry is helpful for all BI related problems:
com.sap.portal.visualcomposer_BIKit_Logger (VC BIKit)
For other issues, see the components and what they do.
Visual Composer 6.0 components:
Portal / J2EE
*com.sap.visualcomposer.portalcontent.sda – Visual composer definitions in the
portal
*com.sap.visualcomposer.portalpermissions.sda – VCRole permissions
com.sap.visualcomposer.sda – HTMLB runtime and portal connector
Design Time
sap.com~vc_client.ear – source files
VisualComposerHelpEar.ear – help context
Server
*vc_ds_service.sda – dev server
VisualComposerServerCommonEar.ear – server common to 04 and 05
VisualComposerServerEar04.ear – Visual Composer 04 server
BI
BIUDISystems.sda – BI kit
com.sap.visualcomposer.BIKit.sda - BI kit
Visual Composer 7.0 components:
Visual Composer 7.0 requires NW04s SPS7 or NW04 SP17.
To Install VC 7.0 on an SPS7 Portal:
Deploy the VisualComposer files in this order. It might be installed with SPS7 by default
(not sure yet).
• VCFRAMEWORKxxx.sca
• VCBASExxx.sca
• VCFLEXxxx.sca
It will deploy the following development componenets:
• com.sap.visualcomposer.portaladdons
• com.sap.vc.portaladdons.BIKit
• VisualComposerServerEar04
• com.sap.visualcomposer.portalpermissions
• vc_ds_service
• com.sap.visualcomposer.portalcontent
• sap.com~vc_client
com.sap.visualcomposer.mmcompiler
Required components from SPS7 that VC utilizes:
BIUDI07_0-XXXX.SCA
com.sap.portal.connectors.ws.sda
com.sap.portal.services.api.sda
com.sap.portal.services.internal.api.sda
tc_sec_destinations_interfaces.sda
tc_sec_destinations_service.sda
tc_sec_wssec_api.sda
tc_sec_wssec_service.sda
If you use the Web Service systems directly from VC, these components are
utilized.
webservices.sda
webservices_api.sda
webservices_lib.sda
If you use the Web Service systems directly from VC, these components are
utilized.
com.sap.netweaver.bc.uwl*
For Portals prior to SPS7, we may be able to deploy these components to SPS7 and VC
should work. Have not tested this. These configuration changes may be needed prior to
SPS7 as well:
1. Open Visual Administrator- > HTTP Provider service.
2. Add to the Mime property : {.htc,text/x-component}
3. Update and save change.
8.4
How to View Logs (and where Logs are located)
1. Start the Standalone Logviewer by
double clicking on the file
logviewer.bat
2. Browse to the correct log you want
to see and double click.
Location of common logs:
Default Trace is located at:
usr\sap -> <SID>\DVEBMGS01\j2ee\cluster\server0\log\defaultTrace.trc
Java RFC Traces are located at:
usr\sap -> <SID>\DVEBMGS01\j2ee\cluster\server0\dev_jrfc.trc
Visual Composer Logs are located at:
usr\sap -> <SID>\DVEBMGS01\j2ee\cluster\server0\log\vcserver\vc.log
www.sap.com/netweaver