This document describes known problems with Oracle ATG Web Commerce Campaign Optimizer 10.1. Where applicable, the problem report number is included in parentheses. Please refer to this number if you need to contact Oracle Technical Support for ATG Products.
(13310926) ATG Campaign Optimizer does not support Internationalized Domain Names (IDN), which are domain names that contain at least one label that is displayed in a language-specific script or alphabet.
Workaround: Use URLs that contain only ASCII characters with ATG Campaign Optimizer.
(13286652) Tests migrated from ATG Campaign Optimizer 9.0 cannot be added to a project in the ATG Business Control Center.
When you try to save a migrated test in a project, you may encounter a problem where the test is not marked “in current project.”
Workaround: If you cannot add a migrated test to a project in the ATG Business Control Center, create a new project in the ATG Business Control Center and copy the migrated test to the new project.
(13286462) (IBM WebSphere application server only) The Registry Admin link displays the View Tests page.
The first time you click the Registry Admin link in the ATG Campaign Optimizer section of the ATG Business Control Center Operations menu, the View Tests page displays instead of the Registry Administration UI.
Workaround: Click the Registry Admin link again. The Registry Administration UI now appears.
(13286371) (IBM WebSphere application server only) The standalone ATG Campaign Optimizer URL does not always redirect to the ATG Business Control Center in Microsoft Internet Explorer 6.
Workaround: Follow these steps to access the ATG Business Control Center:
Point your Web browser to the URL that represents the ATG Business Control Center. The URL you enter depends on the application server on which ATG Campaign Optimizer is running. The default URLs are as follows:
JBoss Application Server: http://hostname:8080/atg/bcc
IBM WebSphere: http://hostname:9080/atg/bcc
Oracle WebLogic: http://hostname:7001/atg/bcc
For example, if you are pointing to the ATG Business Control Center on WebSphere on your local machine, which is common for product evaluation, enter http://localhost:9080/atg/bcc.
(13279224) Page picker UI does not show pages from running Web applications.
When you are creating tests that show different pages to different users, you may encounter a problem where pages from Web applications that you run as standalone EAR files do not appear in the ATG Campaign Optimizer Test Element screens. Only pages in the root folder “/” appear.
Workaround: Follow the steps below, replacing references to the example application, Sketch, with your Web application:
In your deployed standalone EAR file, navigate to the following directory (which is equivalent to the DYNAMO_HOME directory in standalone mode):
<StandaloneEARFileRoot>/atg_bootstrap.war/WEB-INF/ATG-INF/home
Ensure that inside localconfig, you have set the following:
/atg/devtools/ContainerAppDirectoryAgent.directoryRoots =
<StandaloneEARFileRoot>/atg_bootstrap.war/WEB-INF/ATG-INF/
Add a copy of sketch.war from <StandaloneEARFileRoot> to <StandaloneEARFileRoot>/atg_bootstrap.war/WEB-INF/
ATG-INF/commerce/b2cblueprint/sketch/j2ee-apps/sketch
Add a copy of the Sketch application.xml file to <StandaloneEARFileRoot>/atg_bootstrap.war/WEB-INF/
ATG-INF/commerce/b2cblueprint/sketch/j2ee-apps/sketch/
META-INF/
Restart your server.
(13294320) In some circumstances, you cannot log out of ATG Commerce Reference Store (CRS) while ATG Campaign Optimizer tests are running. For example, if you are running a test that replaces the page index.jsp.
Workaround: Be careful which pages you replace when creating test definitions. If the problem persists, stop all ATG Campaign Optimizer tests before logging out of CRS.
(13290567) Deploying a test to the production server, reverting, and then redeploying the test results in errors.
The production cannot tell the difference between trying to run a test more than once (which is not allowed) and redeploying a test.
Workaround: Do not redeploy a test to the production server. Instead, create a new test and deploy it.
