Professional Documents
Culture Documents
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. contained in this document serves informational
purposes only. National product specifications may vary.
No part of this publication may be reproduced or
transmitted in any form or for any purpose without the These materials are subject to change without notice.
express permission of SAP AG. The information These materials are provided by SAP AG and its affiliated
contained herein may be changed without prior notice. companies ("SAP Group") for informational purposes
only, without representation or warranty of any
Some software products marketed by SAP AG and its kind, and SAP Group shall not be liable for errors or
distributors contain proprietary software components of omissions with respect to the materials. The only
other software vendors. warranties for SAP Group products and services are those
that are set forth in the express warranty statements
Microsoft, Windows, Outlook, and PowerPoint are accompanying such products and services, if any.
registered trademarks of Microsoft Corporation. Nothing herein should be construed as constituting an
additional warranty.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, These materials are provided “as is” without a warranty
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent of any kind, either express or implied, including but not
Miner, WebSphere, Netfinity, Tivoli, and Informix are limited to, the implied warranties of merchantability,
trademarks or registered trademarks of IBM Corporation fitness for a particular purpose, or non-infringement.
in the United States and/or other countries. SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or
Oracle is a registered trademark of Oracle Corporation. consequential damages that may result from the use of
these materials.
UNIX, X/Open, OSF/1, and Motif are registered SAP does not warrant the accuracy or completeness of
trademarks of the Open Group. the information, text, graphics, links or other items
contained within these materials. SAP has no control
Citrix, ICA, Program Neighborhood, MetaFrame, over the information that you may access through the
WinFrame, VideoFrame, and MultiWin are trademarks use of hot links contained in these materials and does not
or registered trademarks of Citrix Systems, Inc. endorse your use of third party web pages nor provide
any warranty whatsoever relating to third party web
HTML, XML, XHTML and W3C are trademarks or pages.
®
registered trademarks of W3C , World Wide Web SAP NetWeaver “How-to” Guides are intended to
Consortium, Massachusetts Institute of Technology. simplify the product implementation. While specific
product features and procedures typically are explained
Java is a registered trademark of Sun Microsystems, Inc. in a practical business context, it is not implied that those
features and procedures are the only approach in solving
JavaScript is a registered trademark of Sun Microsystems, a specific business problem using SAP NetWeaver. Should
Inc., used under license for technology invented and you wish to receive additional information, clarification
implemented by Netscape. or support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”)
MaxDB is a trademark of MySQL AB, Sweden. included in this documentation are only examples and
are not intended to be used in a productive system
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other environment. The Code is only intended better explain
SAP products and services mentioned herein as well as and visualize the syntax and phrasing rules of certain
their respective logos are trademarks or registered coding. SAP does not warrant the correctness and
trademarks of SAP AG in Germany and in several other completeness of the Code given herein, and SAP shall
countries all over the world. All other product and not be liable for errors or damages caused by the usage of
service names mentioned are the trademarks of their the Code, except if such damages were caused by SAP
respective companies. Data 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.
1. Go to transaction WSADMIN
7. Hit Test.
8. Run the “GetQueryViewData”
operation.
3 Troubleshooting BW Issues
- Ensure that your BW User ID has S_RS_COMP values for the InfoCube
and Query in Question.
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
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
3. Choose the
“com.sap.portal.systems.BIUDI”
PAR.
2. Go to transaction “SICF”.
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
- Ensure that you’ve created a unique system alias. You cannot have 2
different connections with the same system alias.
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.
With this error, you cannot get a dropdown list of systems in Visual Composer.
You may even get the following error message:
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.
Make sure you deploy BIMMR sca and then BIUDI sca. The order is important.
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.
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.
- 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)
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.
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)
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
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.