When you use JBoss or WebLogic as your application server, you need to build a J2EE application that contains an instance of the modules used by ATG Merchandising. Once you’ve assembled your application, deploy the application to the appropriate location and start it up according to the instructions provided in your application server manuals.
The ATG platform provides an assembly tool that you can use to create your J2EE application. You can find detailed information about assembling a J2EE application that includes the ATG platform in the ATG Programming Guide.
To assemble a J2EE application that includes ATG Merchandising, you execute a command in this format:
<Atg2007.3dir>/home/bin runAssembler [options]output-file-name–mmodule-list
When you build an application that you intend to run with ATG Merchandising, you need to include:
DCS-UIor a submodule of itPubPortletA commerce module that represents a commerce product, such as
B2CCommerce.VersionedorB2BCommerce.Versioned, or a type of catalog (custom or standard).The
- layer Previewswitch, if you want to be able to preview catalog data. For more information on setting up the preview feature, see the Setting Up Preview Features chapter in the ATG Business Control Center Administration and Development Guide.Modules that support the integration of ATG Search, ATG Merchandising, and ATG Commerce, if you have all three products.
Other modules you’ve created that contain your custom code
For example, if you want your application to include ATG Merchandising, ATG Content Administration, and ATG Consumer Commerce using custom catalogs, use this command:
<Atg2007.3dir>/home/bin runAssembler MyApp.ear –m DCS_UI.management
PubPortlet B2BCommerce.Versioned
where MyApp.ear is your application packaged as a J2EE archive file. This command assumes that you have not created any custom modules or use additional ATG modules because if you had, they would have been specified here. Only the modules mentioned here and those accessed by them are included in the EAR file. Remember that you can start only the modules that are included in your J2EE application so if you designate one module during assembly only, you won’t be able to start other modules without assembling a new J2EE application.
Here’s an example of the command you’d use to run ATG Search with ATG Consumer Commerce, so you can use Dynamic Search and Navigation as well as Search Merchandising:
<Atg2007.3dir>/home/bin runAssembler MyApp.ear –m DCS-UI.Search
PubPortlet B2CCommerce.VersionedDCS.Search.Versioned
The corresponding ATG Business Commerce command is as follows:
<Atg2007.3dir>/home/bin runAssembler MyApp.ear –m DCS-UI.Search PubPortlet
B2BCommerce.Versioned DCS.Search.CustomCatalogs.Versioned
Because ATG Merchandising is a development application, you do not need to include it when you are assembling your production application. The command to create a production ear file for one application in a cluster that uses ATG Business Commerce and ATG Content Administration is as follows:
<Atg2007.3dir>/home/bin runAssembler MyApp.ear –m DCS.PublishingAgent
B2BCommerce
For information on how to deploy your J2EE application, see the documentation from your application server vendor.
