How to Resolve Visual Composer Issues

8/9/2019 How to Resolve Visual Composer Issues

http://slidepdf.com/reader/full/how-to-resolve-visual-composer-issues 1/60

l

How-to Guide

SAP NetWeaver ‘04

SAP NetWeaver 2004s

How To…Resolve Visual

Composer

IssuesDOCUMENT 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 theexpress 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 warrantyof 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 provideany 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 andare 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 VisualComposer problems. This paper shows how to identify the true source of problems and

lists common issues and resolutions.

2 Identi fy 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 ifit isn’t already there and hit Save.

4. Browse to “SOAP Application forRFC-Compliant FMs ->query_view_data -> Data for the

query view” and hit Run.

5. Choose “Document Style” and hitthe Green Check.



6. Login with your username andpassword and hit Submit.

7. Hit Test.



10. Make sure a successful response isreturned. If this is successful, BW isconfigured properly. If this is notconfigured properly, go to thesection on troubleshooting BWIssues.

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 InfoCubeand Query in Question.

- Ensure that your BW User ID has the S_DEVELOP values specifiedbelow.

3.2 “ Virtual Interface not found” error



This error will give you a message such as:"Err or 32010: Cannot execut e quer y. No r esul t r eturned or XML r etur nedi n t he r esul t cont ai ns an er r or . Vi r t ual I nt er f ace not f ound. "

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 GreenCheck.



3. Hit the “Activate” button toregenerate your Virtual Interface.

3.3 “ Serialisation” error

1. Go to transaction SICF and choose“External Aliases”.

2. Delete and recreate the externalalias“/default_host/sap/bc/srt/rfc/sap/quer y_view_data”.



3. Go to transaction SE80 and choose“Edit Object”.

4. Choose “Enterprise Services” andspecify the Web Service Definition“QUERY_VIEW_DATA”. Hit theGreen Check.



5. Click on the “Properties” Tab.Double click on the“query_view_data” Virtual Interfaceto 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 hitback.

9. Activate the “Virtual interface” andhit 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 havebeen acquired from the softwarevendor and installed on the server. Ifthe JDBC driver was not set up, itcan be added by clicking on the“Create Driver” button the cursor isover in the diagram to the left andentering a name for the driver.

3. Add the jar files to the driver entryand Click OK.



4. The new driver will then appear. Wehave now added a driver to be usedin our BI Connector.

5. Verify the BI JDBC ConnectorResource Adapter exists. We cansee that the BI JDBC Connector is

active and running with the defaultsset.

6. To create a new connector, selectthe Connector SDK_JDBC and clickthe Clone button to create a new BIJDBC Connector and enter a namefor the connector.



7. Select the recently createdConnector and choose the Resource Adapter tab. Click the Add button toassociate additional Resources withthe Connector

8. To add resources, enter the name ofa Resource we wish to associatewith the Connector.

9. Login to the Portal.



10. Create a New System on the Portal.Go to “System Administration ->System Configuration” and click on afolder. Then create a System bychoosing “New from Par -> System”.

11. To create a BI JDBC System withinthe Portal, select the“com.sap.portal.systems.BIUDI”

PAR and choose Next.

12. Select the “SAP_BI_JDBC” optionand choose Next.



13. Enter a System Name, ID and Prefixand choose Next. Then ChooseFinish and Open the Object forEditing.

14. Navigate to the Connectionproperties option in the PropertyCategory dropdown list. Enter in the

database connection URL, do notforget to specify the DatabaseNameyou wish to connect to in the URLstring. Enter in the Driver Classname.

15. Navigate to the User ManagementProperty Category and choose theadmin,user option.



16. Verify the ConnectionFactorycreated in step 1 “MSSQL_JDBC” isspecified under the “Show All”Property Category.

17. From the Display dropdown listchoose the System Aliases option.Enter an alias for the system and

choose the add button. Don’t forgetto save.

18. To create user mapping, Navigate tothe User Administration -> UserMapping tab and enter yourusername and choose Start.



19. Once you have found your userchoose the Edit button. Choose theBI JDBC System created. Enter userand password information for thissystem and save your settings.

20. To test the connection, navigateback to the System Configurationarea. Choose the BI JDBC System

you created. Navigate to theConnection Tests area and choosethe Test Button. This should besuccessful.

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.OracleDriverURL: jdbc:oracle:<drivertype>:@<database> jdbc:oracle:thin:@myhost:1521:orcl

4.3 BI JDBC Connector to MaxDB

Driver: com.sap.dbtech.jdbc.DriverSapDBURL: 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.CsvDriverURL: jdbc:relique:csv:c:\\csv

4.5 BI SAP Query Connector

1. To verify that you have created aninfoset with available data, login toyour backend system. Navigate totransaction sq02. Identify the InfoSetwhich you will configure yourDataService on top of. Verify there isdata within the InfoSet.



2. Login to the portal. Create a NewSystem 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 andsystem prefix and Open the Objectfor editing.

6. Navigate to the ConnectionProperties Category. Enter the

appropriate information for thelocation of the Application Server,the Message Server, Client andSystem Number. The Query Areaentry determines where you accessdata from

X = Global Area (Cross-client)

‘ ‘ = Standard Area (Client–specific)

Save your information.



7. Under the ‘Info’ Property Categoryenter a Description and SystemName and choose Save.

8. Navigate to the ‘UserManagement’Property Category and specify the

User Mapping Type (e.g.admin,user) and Save yourinformation.

9. Within the System Alias Editorcreate a System Alias. Save yourinformation.



10. To configure the user mapping to thebackend system, Navigate to theUser Administration -> UserMapping tab and enter yourusername and choose Start.

11. Once you have found your userchoose the Edit button. Choose the

BI SAPQ System created. Enteruser and password information forthis system. Save your settings.

12. To test the connection, Navigateback to the System Config area.Choose the BI SAPQ Systemcreated. Navigate to the ConnectionTests area. Choose the Test Button.

4.6 BI ODBO Connector



1. Verify you have ODBO system toconnect to. Connect to yourMicrosoft Analysis Service runningon your SQL Server. Identify yourCatalog you will connect to. Identifya cube which you want to use to

retrieve data from.

2. A good trick to figure out yourconnection string to your ODBO

system is to create a udl (universaldata link) file.

3. You can do this by creating a newtext file and giving it the .UDL suffix.



4. From here you can specify yourconnection properties and test yourconnectivity to Microsoft AnalysisServices (or SAP Netweaver BI)

5. After configuring this UDL file andtesting the connection successfullyyou can send the file to notepad toread the embedded connectionstring.



6. You now have a connection stringfor the ODBO Connector you areabout to create.

7. Login to the portal and Create a NewSystem from PAR

8. Choose the BIUDI PAR



9. Choose the SAP_BI_ODBO Systemtype

10. Give the system a name, ID andsystem prefix and Open the Object

for editing.

11. Navigate to the ConnectionProperties Category. Enter theconnection string we created in step1. Save your information.



12. Navigate to the User Managementtab, set up the User Mapping Type.Save your information.

13. Create a system alias from theSystem Alias Editor.

14. Navigate to the User Administration -> User Mapping tab. Enter yourusername and choose Start.



15. Once you have found your userchoose the Edit button. Choose theBI ODBO System created. Enteruser and password information forthis system. Save your settings.

16. Navigate back to the System Configarea. Choose the BI ODBO System

created. Navigate to the ConnectionTests area. Choose the Test Button.

4.7 BI XMLA Connector



1. Login to the SAP BW system youwill 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 SAPNetWeaver Web Application Serveris running, we can now create a BIXMLA System.

6. Navigate to transaction SMICM –The ICM Monitor



7. Select the service HTTP or HTTPSyou will use to connect to the WebServer. Display the Service.

8. Concatenate the Protocol Hostname and port to create the 1st part

of our URL (iehttp://iwdf9484.wdf.sap.corp:54080)

9. Navigate to transaction SICF – TheInternet Connection Framework



10. Find your way to the XMLA serviceonce again. Display the Service. Thepath to the service is listed here.Concatenate the string after/default_host/ to the end of the URLwe have built. Add XMLA on to the

end of the URL to access the ICFobject / XMLA Service (iehttp://iwdf9484.wdf.sap.corp:54080/sap/bw/xml/soap/xmla)

11. Login to the portal. Create a NewSystem from PAR

12. Choose the BIUDI PAR



13. Choose the SAP_BI_XMLA Systemtype

14. Give the system a name, ID andsystem prefix and Open the Object

for editing.

15. Navigate to the ConnectionProperties Category. Enter the URLwe built in step 2. Save yourinformation.




17. Create a system alias within theSystem Alias Editor. Make sure you

Save.




19. Once you have found your userchoose the Edit button. Choose theBI XMLA System created. Enter userand password information for thissystem. Save your settings.

20. Navigate back to the System Configarea. Choose the BI XMLA System

created. Navigate to the ConnectionTests 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 orhigher. For Visual Composer 7.0, ensure your support pack is SAP BW 3.5 SP14or higher and Enterprise Portal is 6.0 SP14 or higher.



1. Navigate to transaction SMICM –The ICM Monitor

2. Select the service Protocol HTTP orHTTPS you will use to connect to

the SAP Web Application Server.Display the Service

3. Login to the portal. Create a NewSystem.



4. Choose the SAP System usingdedicated application server Systemtype.

5. Give the system a name, ID andsystem prefix. Open the Object forediting.

6. Navigate to the Web ApplicationServer Property Category. Enter theWAS Description, Host Name, Pathand Protocol which we determined instep 1.




8. Navigate to the Connector PropertyCategory. Enter the Application host

(this was determined this in step 1).Enter the Gateway Host (generallythe Application Host). Enter theGateway Service (Concatenation ofSAPGW and System Number).Enter the Logical System Name,Client, System ID and SystemNumber.



9. The System Type must be set toSAP_BW. Save the information.

10. Create a system alias within theSystem Alias Editor




12. Once you have found your userchoose the Edit button. Choose theSAP R3 Dedicated Server System oftype SAP_BW created. Enter userand password information for thissystem. Save your settings.

13. Navigate back to the System Configarea. Choose the SAP R3 Dedicated

Server System created. Navigate tothe Connection Tests area. Selectthe SAP Web AS Connection andthe Connection Test for ConnectorsTests. Execute the Test. You arenow 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 2different connections with the same system alias.

- Check User Mapping – SSO or UIDPW?



6.2 Check Secure Store

1. Login to the Portal and navigate toSystem Administration -> SystemConfiguration -> UM Configuration -> Direct Editing

2. Check your secure store setting andensure that it mirrors your encryptiontype (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 testthe connection between the Portal and the Visual Composer Server. Makesure 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 orrecurring login screens are returned without the login succeeding.



3. Login to the Portal and navigate toSystem Administration -> SystemConfiguration -> UM Configuration -> Direct Editing

4. Change login.ticket_include_cert=1to login.ticket_include_cert=0. If this

isn’t included in the file, then addentry login.ticket_include_cert=0. Afterwards, restart the J2EE.login.ticket_include_cert=1 is adeprecated function. It saves thecertificate in the logon ticket, and insome cases this ticket is too big toset 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 -> SecurityProvider

3. Choose the “Security Roles” tab.

4. Choose component “SAP-J2EE-Engine”.



5. Choose the “administrators” role andchoose the “Add” under Users.

6. Specify “J2EE_ADMIN” and hitSearch. Choose “J2EE_ADMIN” and

hit OK.



7. Make sure the “J2EE_ADMIN” userexists under Users.

8. Choose KeyStoreViewCreator andmake 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 note598891.

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 mi ssi ng XML Obj ect "

In many cases, this is due to UME issues. Check the logs to see if VisualComposer tries to login to the Portal using the user “Guest”. This would failbecause “Guest” isn’t an authorized user in the Portal. To check the logs, see thesections 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 thedefaultTrace.trc file.


2. Go to Server -> Services -> SecurityProvider

3. Under “components”, choose“ticket”.



4. In change mode, choose“com.sap.core.server.jaas.EvaluateTicketLoginModule” 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 UMEconfiguration, seehttp://help.sap.com/saphelp_nw04/helpdata/en/cb/ac3d41a5a9ef23e10000000a155106/content.htm

6.7 Cannot Retrieve InfoAreas error

"Err or - 32002: Cannot r et r i eve i nf oar eas.Servi ce not f ound:com. sap. port al . gui machi ne. BI Ki t . 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 ComposerServer, the Enterprise Portal Server, and the client machine.

7.2 Cannot See Anyth ing within the Visual Composer Storyboard?



- Ensure that the Adobe SVG Viewer is installed on the client machine.-

7.3 No Visual Composer was found at specified address

"Fat al Er r or : No Vi sual composer was f ound at speci f i ed addr ess

Err or r eadi ng server parameters i n ur l : bi n/ gm1433030. asp"

This is because the file “~server.ini” is not accessible by the program. Make surethe ~server.ini file is accessible by the browser by tryinghttp://<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 "AccessDenied" error is raised in the browser (Javascript Error). Visual Composer is notloaded

Current available workaround: Add the domain name to the trusted sites in thebrowser'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)

- Ensure that the Portal UserId has the VCRole assigned.

7.7 Flash compilation error:

If you get this error:

Er r or i n execut i ng a pr ocess f or Fl ex compi l at i on, War ni ng: Mi ssi ngchar set s i n St r i ng t o Font Set conver si onWarni ng: Cannot conver t st r i ng "- dt - i nt erf ace syst em- medi um- r - nor mal - s*-*- *- *- *- *- *- *- *" t o t ype Font SetWar ni ng: Cannot conver t st r i ng "- monot ype- ar i al - r egul ar - r - nor mal *- 140-*- *- p- *- i so8859- 1" t o t ype Font St r uctWarni ng: Mi ssi ng charset s i n St r i ng t o Font Set conver si onWar ni ng: Cannot conver t st r i ng "- dt - i nt er f ace user - medi um- r - nor mal - s*- *-*- *- *- *- *- *- *" t o t ype Font Set



Or this error:

Er r or i n execut i ng a pr ocess f or Fl ex compi l at i on, j ava. l ang. I nt ernal Er r or : Can' t connect t o X11 wi ndow server usi ng ' : 0. 0'as t he val ue of t he DI SPLAY vari abl e.

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 WindowToolkit) to implement compile time image embedding and SVG. By default, theJava Virtual Machine tries to use the hardware-based graphical capabilities of themachine to implement AWT. For servers without a graphical interface, the aboveerror 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.sap.vc.mmcompiler\res\root\WEB-

INF\flex\flex-config.xml”

2. In the <compiler> element, find the<headless-server> parameter, andchange it's value to true. Around line#146, change <headless-server>false</headless-server> to<headless-server>true</headless-server>



8 Stil l Have Problems?

8.1 How to Turn on Logs for Visual Composer 6.0

3. Open up the “~server.ini” file in theIIS Server directory. If your root is“C:\Intepub\wwwroot\”, then the fileis located at“C:\Inetpub\wwwroot\SAPNetWeaver VisualComposer\server\~server.ini”.

4. Change the LogLevel to “0”. Thedefault value is “2”. Save this file.




6. Go to “server -> services -> Logconfigurator”

7. See the matrix within this documenton the specific errors and logs toturn on. Make sure you turn the logseverity to “All” for the componentyou are having issues with.



8.2 How to Turn on Logs for Visual Composer 7.0


2. Go to “server -> services -> Logconfigurator”

3. Go to the “Locations” tab.



4. Go to com -> sap -> portal ->connectors and turn up the severityto “All” for connection issues.

5. Go to com -> sap -> portal -> vc andturn up the log severity to “All” forany runtime, designtime, or HTMLBissues.



6. Go to com -> sap -> portal -> uddifor any issues with soap service andturn up the logging severity to “All”.

7. For general Visual Composerissues, go to com -> sap -> portal ->

visualcomposer and turn up thelogging severity to “All”.

8. For any other issues, including UME,and SSO, see the log matrix to seewhich 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 forthe 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 theportal*com.sap.visualcomposer.portalpermissions.sda – VCRole permissionscom.sap.visualcomposer.sda – HTMLB runtime and portal connector

Design Timesap.com~vc_client.ear – source filesVisualComposerHelpEar.ear – help context

Server*vc_ds_service.sda – dev serverVisualComposerServerCommonEar.ear – server common to 04 and 05VisualComposerServerEar04.ear – Visual Composer 04 server

BI BIUDISystems.sda – BI kitcom.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_clientcom.sap.visualcomposer.mmcompiler

Required components from SPS7 that VC util izes:BIUDI07_0-XXXX.SCAcom.sap.portal.connectors.ws.sdacom.sap.portal.services.api.sdacom.sap.portal.services.internal.api.sda

tc_sec_destinations_interfaces.sdatc_sec_destinations_service.sdatc_sec_wssec_api.sdatc_sec_wssec_service.sda

If you use the Web Service systems directly from VC, these components areutilized.

webservices.sdawebservices_api.sdawebservices_lib.sda

If you use the Web Service systems directly from VC, these components areutilized.

com.sap.netweaver.bc.uwl*

For Portals prior to SPS7, we may be able to deploy these components to SPS7 and VCshould work. Have not tested this. These configuration changes may be needed prior toSPS7 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 bydouble clicking on the filelogviewer.bat

2. Browse to the correct log you wantto 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

How to Resolve Visual Composer Issues

Documents

Transcript of How to Resolve Visual Composer Issues