Assess the requirements of your staging and production
environments and adjust the
AppConfig.xml file in the Deployment Template to point
to the correct host names for your servers.
This topic provides high-level steps. For additional information on customizing the Deployment Template, see Configuring an EAC Application.
To configure your server topology:
Analyze your goals for the performance of your Guided Search application. Look at the projected size of the data set and other characteristics. For detailed information on hardware benchmarking and performance, see the Oracle Commerce MDEX Engine Performance Tuning Guide.
Formulate the requirements of your staging and production environments, based on your goals for the expected performance.
For example, you will need to have an estimate of how many servers must be provisioned in the staging and production environments, and how many MDEX Engines you will need to run on each of the MDEX Engine servers. In the staging environment, you may want to provision a full duplicate of your expected production environment, or it may be sufficient to provision a subset of your production servers in a staging environment.
Note
The Workbench server requires a separate thread for each Assembler client. If you configure a large number of Assembler clients (50+) for your application or applications, you must ensure that the Workbench server has adequate memory. This may require more than the recommended 4 GB.
Proceed to configure your server topology for both staging and production environments. You do this by adjusting the Deployment Template
AppConfig.xmlfile so that it points to the correct host names for your servers.You will typically run the Deployment Template
deployscript in each environment, configuring each environment as a self-contained project.
After you finish adjustments to the servers, you can configure your application using the Deployment Template and start customizing the baseline update script for your project.
