Copyright © Cloud Software Group, Inc. All Rights Reserved

Deploying Your Custom Application

The following lists the files/directories that need to be deployed with your custom WCC application:

   WCCProjectName.html

   logger.xml

   \addins

   \JSX

   \JSXAPPS

      \WCCProjectName

      \wcc

      \ipc

where:

•	WCCProjectName.html is the launch fragment for your custom application, where WCCProjectName is the name you gave the WCC project when creating your custom application in General Interface Builder.

•	logger.xml handles logging iProcess Workspace (Browser) errors.

•	\addins contains the TIBCO Forms add-ins needed at runtime.

•	\JSX contains the General Interface runtime.

•	\JSXAPPS\WCCProjectName contains your custom application, where WCCProjectName is the name you gave the WCC project when creating your custom application in General Interface Builder.

•	\JSXAPPS\wcc contains the WCC components software.

•	\JSXAPPS\ipc contains the base-level code needed by custom applications.

Each of these files\directories need to be deployed, in the structure shown, to the web server that will be hosting your custom application.

Deploying to a Portal

Deploying your custom application to a portal generally involves wrapping the inline DIV created by the General Interface Builder Deployment Utility in the portal page, as appropriate for your portal server.

An example of launching multiple WCC applications in one launch fragment is shown in Starting Multiple Applications from the Launch Fragment. This example simulates a portal environment, except that it launches two applications within one container, rather than each application being launched within a separate portal.

For details about running applications in a specific portal server, refer to the documentation for your portal server.

Copyright © Cloud Software Group, Inc. All Rights Reserved