This appendix provides information to help if you have trouble installing multiple applications.
The table below provides descriptions of messages that you might see or problems that you might encounter when installing and running multiple applications.
For additional troubleshooting information that is specific to the ATG products you are using, refer to the documentation for those products.
Symptom | Potential Problem | Possible Solution |
|---|---|---|
Stack traces are thrown when a server attempts to run a scenario at start-up on ATG JBoss installations. | When a server attempts to run a scenario at start-up, and the scenario elements needed to run the scenario (such as events and actions) are not defined in the server’s config path, error traces are thrown. Note that the scenario runs correctly. | You can ignore the errors, or to start the server without these errors occurring, ensure that all scenario elements are defined in the server’s config path. For details about scenario events associated with ATG applications, refer to the application documentation (see About the Applications for a list of application documentation). For details about setting up scenarios, see Scenarios Module Programming in the ATG Personalization Programming Guide. |
When creating database schema, you see a message about tables already existing. | This could be a result of running the same script twice when creating your database schema. Some applications share the same underlying framework and running the same script (or scripts containing duplicate information) twice generate messages about tables already existing. Usually this will not cause problems; however it is good practice to avoid running scripts more than once. | See Create Database Schema and your application documentation to determine if there are duplicate scripts in your installation instructions (that you ran more than once). |
When importing data, you see a message about not being able to import a project because a project with that name already exists. | This could be a result of attempting to import the same data twice. Usually this will not cause a problem; however it is good practice to avoid importing data multiple times. | See Import Initial Data and your application documentation to determine if there is duplicate data (that you attempted to import more than once). |
Scenarios or ATG Outreach campaigns do not run as expected. | If your environment includes ATG Service, make sure that you started your servers in the correct order. The customer-facing server must be started before the agent-facing server. | Refer to Order of Server Startup for Correct Behavior of Scenarios for more information. |
