After you have verified that the system and the product upgrades are complete, perform the "clean-up" tasks described in this section.
System Maintenance:
1. Delete obsolete product files (recommended)
Applies to 11i release level: All TUMS step key: N/A
Delete the product files for the previous release (if you have not done so already).
You may want to retain report output files or customized programs. Output files are stored in the old log and output subdirectories under each product's top directory, under the log and output directories you created, or under a common directory.
To remove obsolete files for an old release, change to the top directory of that release and enter the following command:
UNIX:
$ rm -rf <old APPL_TOP>
Here is an example:
$ rm -rf /d01/appl/r10 Windows:
C:\> del /s /q <old APPL_TOP>
Here is an example:
C:\> del /s /q \APPL110
2. Register new products (conditional)
Applies to 11i release level: All TUMS step key: N/A
New products added since Release 11i was initially made available (May 2000) are not automatically registered in the database. If you intend to use new products, register them using License Manager. See Oracle E-Business Suite Maintenance Guide for instructions.
3. Update Java Color Scheme profile option for selected users (conditional)
Applies to 11i release level: All TUMS step key: N/A
By default, the Java Color Scheme profile option should be set to "standard" for all sessions for optimal system response time. The upgrade process sets this default value for all instances. However, setting this profile option to a different value may work better for some systems. See Oracle E-Business Suite Setup Guide and Oracle E-Business Suite User's Guide for more information.
4. Complete Workflow Notification Mailer configuration (required) Applies to 11i release level: All
TUMS step key: MP_WORKFLOW_TASKS
Before you send Oracle Workflow e-mail notifications, you must complete the Workflow Notification Mailer configuration, using the Notification Mailer Configuration wizard in Oracle Applications Manager.
1. Log on to Oracle Applications Manager.
2. From the Applications Dashboard, select the Workflow Manager from the
"Navigate to" pull-down menu. Click Go.
3. In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page. The Notification Mailers status icon should show a status of Down.
4. On the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the notification mailer configuration wizard.
5. In the Outbound Email Account (SMTP) region, enter the name of the outbound SMTP mail server.
6. If you want to enable inbound e-mail processing, select the Inbound Processing parameter in the Inbound Email Account (IMAP) region, and enter the name of the inbound IMAP mail server, user name and password of the mail account that the notification mailer uses to receive e-mail messages, and the reply-to address of the e-mail account that receives incoming messages, to which notification responses should be sent.
7. Click Apply.
8. Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component status is Running.
Note: See Oracle Workflow Administrator's Guide for more
information.
If you have previously implemented the C-based Notification Mailer concurrent program or the Generic Service Management Notification Mailer, the tag definitions and configuration parameter settings for those parameters that are still applicable are automatically transferred to the Java-based Workflow Notification Mailer configuration parameters.
5. Complete Transport Agent setup (conditional) Applies to 11i release level: All
TUMS step key: N/A
If you are using a proxy server to handle your outbound Oracle Transport Agent requests, then set following OXTA parameters in the container configuration:
• OXTAOutUseProxy=True
• OXTAOutProxyHost=<Your proxy server name>
• OXTAOutProxyPort=<Your proxy server port>
To set the parameters, go to the Oracle Applications Manager Site Map and choose AutoConfig > Applications Node > Edit Parameters. Then, use the Search field to find OXTA. After you set the parameters, run AutoConfig to regenerate the wls.properties file
(FMW_Home/Oracle_EBS-app1/applications/oafm/APP-INF/wls.properties).
Note: See Oracle XML Gateway User's Guide for more information.
6. Complete setup for Oracle XML Gateway (required) Applies to 11i release level: All
TUMS step key: N/A
The Oracle XML Gateway engine uses style sheets from an operating system directory you specify in the UTL_FILE_DIR database initialization parameter for your Applications instance. You must also specify the same directory in the ECX:
XSLT File Path profile option. The value you specify for both the parameter and the profile option must be an absolute path and cannot contain a symbolic link or other operating system-specific parameters.
Also, ensure that the following profile options are set at site level for Oracle XML Gateway. If you have previously set these profile options, then no action is necessary, as the upgrade preserves these values.
Profile Option Description
ECX: XSLT File Path Path to the directory specified as the location for style sheets to be used for XSLT transformations. It must be one of the valid values specified in the UTL_FILE_DIR database initialization parameter. Ensure that there is no slash at the end of the directory name.
ECX: System Administrator Email Address Address to which Oracle XML Gateway error notifications should be sent.
ECX: Server Time Zone Time zone the database server is running in.
Note: See Oracle XML Gateway User's Guide for more information.