Customizing Scenarios and Messaging

If you are running with ATG Knowledge, and you want to create custom scenario- or messaging-related code, you need to make sure that your code is in modules that are loaded on both servers, and you need to make sure that your data is stored in the svcshared database tables. This includes customizations to any of the following ATG entities:

If your customizations are for external scenarios only, and you are using ATG Knowledge, you need to make sure that your ATG Knowledge server loads the code. It is not sufficient to add the customizations to the Self Service server, because the ATG Knowledge server will not notice them, and will fail to launch the external Scenario Manager, causing your customizations to be ignored. Use the scenarioManager.xml file to register such customizations, and load this file on both the Knowledge and Self Service servers.

When creating custom events and actions, keep in mind that the ATG Knowledge and ATG Self Service implementations are very similar; they use the same set of methods to work with scenario events. They share the atg.svc.agent.events.EventTools event logging mechanism with minor variations:

Both ATG Knowledge and ATG Self Service use a database called svcshared, where data necessary for both applications is stored. These tables store scenario- and messaging-related data.

 
loading table of contents...