Installation Logging and Troubleshooting 

You can find information about log files and troubleshooting when installing components on Application Server Java at SAP Service Marketplace at service.sap.com/installnw70 and in the Installation - SAPNetWeaver Systems section, choose the Java link from the appropriate bullet.

The following sections provide assistance in troubleshooting problems that may arise after running Visual Composer for the first time after installing the EP usage type on a clean machine.

SECTION: PREREQUISITESYou have access to the following systems:

SUBBULLET HTTP – connection to the J2EE Engine

SUBBULLET J2EE Engine directly through terminal server, NetMeeting or PCAnywhere

BULLET You have Content Administrator rights to the J2EE Engine

SUBSECTION: MAIN TOOLSDM remote GUI

SUBSECTION: ANALYSIS

...

...

       1.      BOLDCheck that the host can be reached when J2EE is running.

LISTCONTINUE Open a command window on your machine and enter ping <hostname> to test if it is possible to reach the host (identified by hostname) on the J2EE machine. If an error occurs, contact your network administrator to fix the problem.

LISTCONTINUE If you have no access to the machine on which the problem exists, refer to the relevant Problem Analysis Scenario (PAS) of the J2EE Engine, accessed on SAP Service Marketplace at service.sap.com/operationsnw70  →  Cross-NetWeaver  →  SAP NetWeaver Problem Analysis Guide (PAG)  →  J2EE Engine Problem Analysis Scenarios.

       2.      BOLD Access the J2EE Engine.

LISTCONTINUE Start your browser and in the address bar, enter:

LISTCONTINUE http://<hostname>:<port>/index.html

LISTCONTINUE where port is the application port number on the J2EE engine in use by the Visual Composer Server installation (default is 5<instance no.>00).

LISTCONTINUE The start page of the J2EE Engine should be displayed. If it is not, the engine has not started. In this case, start the J2EE Engine.

       3.      BOLD Determine if the problem is a client or a server issue.

LISTCONTINUE Because Visual Composer Storyboard is a client-server application, the failure may have occurred on the client machine and not in the main server. To ensure that the Visual Composer client can run Storyboard, check that the following has been installed on the client:

SUBBULLET Microsoft XML Parser 4.0

SUBBULLET Adobe SVG Viewer 3.0 or higher

LISTCONTINUE Upon running Visual Composer, if an alert message is displayed indicating that studio.ini is not installed or that the mxml file is not updated, the relevant component has not been properly installed.

LISTCONTINUE These are the main client errors that may arise. If other problems occur, the source is probably on the server side.

       4.      BOLD A Loading server failed message is received.

LIST CONTINUE This message occurs when integration between several server components has failed. In this case:

       5.      SUBNUMBER Redeploy the file VisualComposerServerEar04.

       6.      SUBNUMBER Log on to the SDM remote GUI tool.

       7.      SUBNUMBER Undeploy the file and then redeploy it.

       8.      BOLD Access is denied.

LIST CONTINUE All users who access Visual Composer must be assigned the VC Role, which becomes available in the portal when Visual Composer is installed with the EP usage type. Add and assign the role through the User Management Engine (UME). The process is described fully in the Portal Administration Guide on SAP Help Portal at help.sap.com/nw70 → SAP Library →  SAP NetWeaver Library → Administrator’s Guide →  SAP NetWeaver by Key Capabilities →  People Integration by Key Capability →  Portal →  User Administration →  Role Assignment →  Assigning Roles to Users and Groups.

       9.      BOLD Check logs.

LISTCONTINUE If other errors occur, log on to the J2EE server and check the defaultTrace file in the log folder. Refer to the Trace and Log Files section of the Administration of SAP NetWeaver Visual Composer Guide.