Although these resources are not required, they are provided with your ATG platform installation because they can be useful. Some resources mentioned below enable key portions of the ATG platform that are be accessible if they are not included in web.xml, so read this list carefully.
Changing a Context Root on a Live Site
The contextroot context parameter is a mechanism for making a Web application context root visible to the ATG Control Center. ATG Scenarios relies on this parameter to inform the ATG Control Center about a change made to the context root defined for a live site. See the Setting the Web Application Context Root for Scenarios section of the Configuring Scenarios chapter of the ATG Personalization Programming Guide.
Activating A PageFilter Debugger
The atg.filter.PagefilterDebug parameter signals error information to be tracked in a log when set to true (false is the default). Set this parameter to true if you encounter unexpected behavior and need to provide error information to Technical Support.
Activating Targeted Email
When your site supports targeted email, you need to invoke the InitSessionServlet and map it to the appropriate component. See the ATG Installation and Configuration Guide.
Accessing Dynamo Administration
To access Dynamo Administration, you need to specify AdminProxyServlet and indicate AdminHandler, the first servlet in the Admin servlet pipeline as an initialization parameter. Also, you need to map AdminProxyServlet to the directory which, when requests for pages in it are called, prompts the AdminProxyServlet to execute. For more information, see the Including Dynamo Administration section.
Preventing Profile Swapping
Several ATG applications contain preview features that allow users to test content on a sample user profile. The implementation of this feature requires swapping the profile of the logged-in user with the profile selected for preview. If your Web application does not include preview features, it is recommended that you disable profile swapping by setting the atg.preview context parameter to false in the web.xml file. For more information, see the ATG Personalization Programming Guide.
Tag Libraries
There are two ways to make a tag library available to a Web application. The first way is to put the tag library class files and TLD in the Web application WEB-INF directory and specify the URI value, which matches the value in the JSPs that use the tag library, in the TLD itself. All ATG tag libraries are implemented in this fashion.
The second way uses web.xml to define the tag library URI and TLD location. Again, the URI indicated here must match the one used in JSPs. It makes no difference which method you use.
One benefit to having two ways to implement a tag library is that you can support two URIs. For example, you can use one URI and if you then decide another is more appropriate, you can use that one too. You can do so by declaring the tag library in web.xml with one URI and keeping the tag library files, including the TLD that defines a second URI, in WEB-INF.
This example shows how to declare the DSP tag library in web.xml:
<taglib> <taglib-uri>/dspTaglib</taglib-uri> <taglib-location>/WEB-INF/taglibs/dspjspTaglib1_0.tld</taglib-location> </taglib>
For more information about the DSP tag libraries, see the ATG Page Developer’s Guide.
Web Services
To make Web services available to your J2EE application, you need to declare them in web.xml. It is common practice to define Web services in their own Web application so they are the only resource defined in web.xml. All ATG Web services are implemented in this way. When you create custom Web services in the ATG platform, a new Web application is created for them where they are specified in web.xml.
You can include any of ATG’s prepackaged Web services in an assembled EAR file by including the module that contains the desired services. For example, to include the Commerce services, specify the DCS.WebServices module when you invoke the runAssembler command. To include Web services you created through the Web Service Creation Wizard, use the runAssembler flag –addearfile to specify the EAR file that contains the service.
For more information about ATG Web services, see ATG Web Services and Integration Framework Guide.
