To create a site and agent in the Business Control Center:
If necessary, log onto the Business Control Center. For instructions, see Browsing the Publishing Server.
Expand Content Administration (CA), and then click CA Console.
Click Configuration, and then click Add Site.
Enter the following details:
Site Name: Production
Site Initialization Options: Do a full deployment
Site Type: Workflow target
Add the following repository mappings. To add a repository mapping, select a Source Repository and Destination Repository, then click Add.
Source Repository
Destination Repository
/atg/commerce/catalog/SecureProductCatalog/atg/commerce/catalog/ProductCatalog_production/atg/commerce/claimable/SecureClaimableRepository/atg/commerce/claimable/ClaimableRepository_production/atg/commerce/locations/SecureLocationRepository/atg/commerce/locations/LocationRepository_production/atg/commerce/pricing/priceLists/SecurePriceLists/atg/commerce/pricing/priceLists/PriceLists_production/atg/content/SecureContentManagementRepository/atg/content/ContentManagementRepository_production/atg/multisite/SecureSiteRepository/atg/multisite/SiteRepository_production/atg/seo/SecureSEORepository/atg/seo/SEORepository_production/atg/store/stores/SecureStoreContentRepository/atg/store/stores/StoreContentRepository_production/atg/userprofiling/PersonalizationRepository/atg/userprofiling/PersonalizationRepository_productionNote: Your browser must have Javascript enabled to create these mappings.
Click Save Changes to save your changes and enable the Agents tab.
Click the Agents tab, and then click Add Agent to Site.
Enter the following details:
Agent Name:
ProdAgentTransport URL:
rmi://<ATGProduction_host>:<ATGProduction_rmi_port>/atg/epub/AgentTransportFor example:
rmi://localhost:8860/atg/epub/AgentTransport
Note: The RMI port you enter here should be the same RMI port you specified in Installing the Oracle Commerce Platform.
Click the button with the double-right arrow to include both the
/atg/epub/file/WWWFileSystemand/atg/epub/file/ConfigFileSystemfile systems in the configuration.Click Save Changes.
Click the Back to deployment administration configuration link.
Click Make changes live.
Accept the default, Do a full deployment (data NOT imported), then click Make changes live.
To view your deployment’s progress, under Deployment Administration, click Overview, then click Production to see the percent complete.
After the deployment has finished, proceed to the next section, Checking the Baseline Index Status, to verify that the baseline index initiated after the deployment completes successfully.
Note: If your deployment is not successful, it may be related to the transaction timeout setting in your application server. All supported application servers time out long running transactions by marking the active transaction as rolled back (essentially, by calling setRollbackOnly on the transaction), which could result in problems with Oracle Commerce Platform applications. If your deployment fails, try increasing the transaction timeout setting and resuming the deployment in the Business Control Center. For details on changing your transaction timeout, see Setting the Transaction Timeout on WebLogic, Setting the Transaction Timeout on JBoss, or Setting the Transaction Timeout on WebSphere in the Platform Installation and Configuration Guide.
