To use preview, you assemble the versioned preview application and the ATG Business Control Center with the –layer Preview switch. For example:
runAssembler –liveconfig acme.ear
–layer Preview –m PubPortlet DCS-UI DCS.Versioned MyVrsApp
You can also supply the –layer Preview switch to the StartDynamoOnJBOSS.bat script. For example:
startDynamoOnJBoss.bat –liveconfig –ear acme.ear
–layer Preview -m PubPortlet DCS-UI DCS.Versioned MyVrsApp
Note: In order to simulate a production-like environment, assemble with the liveconfig option.
For full information on runAssembler command options and syntax, see Developing and Assembling Nucleus-Based Applications in the ATG Programming Guide.
Assembling for Non-BCC Servers
If you run the preview application on multiple servers, two requirements apply:
For servers that do not run the ATG Business Control Center, assembly must omit the modules
PubPortletand, if applicable,DCS-UI. In this case, assembly must explicitly include the WebUI module.The data of versioned repositories must be consistent across all servers. In order to ensure that asset and user profile changes on one server are replicated on all, you must enable caching—preferably, distributed or distributed hybrid caching modes—on all server instances. For more information about repository caching modes, see SQL Repository Caching in the ATG Repository Guide.
Note: Never disable caching on versioned repositories for preview applications or use simple caching mode.
For example, you might assemble an application for preview on a non-BCC server as follows:
runAssembler –liveconfig acme.ear –layer Preview –m WebUI DCS.Versioned MyVrsApp
