Skip to main content

Introduction

This document covers the installation process of Wands for Oracle on R12.2 Oracle systems.

The Wands for Oracle comprises a suite of products. The installation process set out below will install all the products although only those that are licensed will be active.

The installation process is executed entirely on the Oracle server. The application is accessed via the normal Oracle logon URL, but from a new Responsibility that is created during the installation process. No Wands software is required to be installed on the client machine.

If you need assistance during the installation process, please contact our support team at e4asupport@insightsoftware.com.

Prerequisites

By installing the software into your system you acknowledge that you accept the terms of the Software License and Maintenance Agreement.

In order to run this version of Wands for Oracle, the following prerequisites must be met: NB Check the Customer Support Community (https://help.insightsoftware.com/s/) for any updates since publishing.

Server Requirements

E-Business Suite Release

E-Business Suite Version

Database Version

Java (JDK)

Oracle E-Business Suite R12**

12.2.x*

11.2 or higher

7 or higher

 

* Requires R12.AD.C.Delta.4 and R12.TXK.C.Delta.4 to address an Oracle bug which affects the servlet installation. Refer to Document 1617461.1 - Applying R12.AD.C.Delta.4 and R12.TXK.C.Delta.4 Release Update Packs.

*  Requires rsync utility be installed as referenced in adop_sync.drv

** We do not currently support Java Access Bridge and require this feature to be disabled. See Oracle Documentation.

Client Requirements

Windows

Browser

Excel Version

Java Runtime Environment

Windows 7 or higher.

 

Wands Launcher

- Edge

- Internet Explorer

- Chrome

- Firefox

Excel 2013 to Excel 2019 and Office 365 (desktop) Semi Annual Pro-Plus Channel including 64bit versions*

 

No longer required.

 

* We recommend the latest updates for all Excel versions.

Upgrade Previous Versions

Upgrading from Version 4

There is no upgrade process from version 4 as the new architecture is completely different from the previous version. This version can be installed independently of version 4 and both can co-exist on an Oracle server during the transition.

Workbooks created in version 4 will need to be upgraded when they are first opened in this version. There is a menu option under the Wands (Oracle) tab to execute this process.

The version 4 key will not work on this version.

Upgrading from 5.4.x

There is no upgrade option from 5.4. You can run the full installation process under section Installation on the Server “Installation on the Server”.

Upgrading from 5.5.x and higher

Note: There is a specific process that must be followed if you are upgrading an Oracle E-Business Suite 11i or 12.x environment to version 12.2.x and Wands for Oracle was already installed on your current 11i or 12.x E-Business Suite instance. In this case you should follow the instructions in the document Installation Guide - Oracle12.2 Upgrade.

There are two upgrade options:

  1. Upgrade using the normal adop patch cycle.

  2. Upgrade using hot mode which is applied directly to the run edition file system and does not require an adop patch cycle.

Upgrade using patch cycle

For this upgrade option you need to follow all the instructions in section Installation on the Server “Installation on the Server” except for section Setup the Excel4apps custom applications “Setup the Excel4apps custom applications”. The custom applications would have been created with the initial install and do not need to be recreated. All the other steps of the installation will be required, including a cutover, in order to follow Oracle’s official patching process.

Upgrade using hot mode

An upgrade using hot mode allows you to deploy a new version of the application without needing to perform all the required steps for a full adop patch cycle.

Follow these steps to perform an upgrade in hot mode

  1. Confirm that both the Excel4apps and Excel4apps Reports Wand applications have been registered on you system.

    1. Log on to the Oracle system and select a responsibility like System Administrator that has permission to register an application.

    2. Navigate to the following menu: Application > Register.

    3. Query the values that start with Excel4apps% and confirm that the two required applications exist.

    4. If a message is displayed, “Forms Registration for Custom Application or schema is now blocked”, then follow step 4.2.2 Verify the Excel4apps custom applications to confirm.

    5. If they do not both exist, follow just the instructions in section Setup the Excel4apps custom applicationsSetup the Excel4apps custom applications and then return here to continue the upgrade process.

  2. Locate the Wands for Oracle install file. This is the complete zip file that was downloaded from our web site (which contained this installation guide). FTP it to the server as the applications user.

  3. Unzip the Wands for Oracle install file.

  4. Navigate to the Wands for Oracle install folder that will have been created by the unzip process.

  5. For UNIX systems, change permissions on the file “install.sh” to allow it to be executed.

  6. Run the Wands for Oracle Installer using the UPGRADE option.

    UNIX:

    ./install.sh --hotpatch UPGRADE

     

    Windows:

    C:\>install.cmd --hotpatch UPGRADE

  7. As the Applications Owner user run the adcgnjar Utility:

[applmgr@oracle122 classes]$ adcgnjar

  1. Enter the APPS username and password when prompted.

  2. The script has completed successfully when the following message is displayed:

customall.jar generated successfully.

  1. For Oracle EBS 12.2.7 or 12.2.6 + Patch 24737426:R12.FND.C ensure that the “Allowed Resources” feature has been configured to grant access to the Wands for Oracle servlets. Refer to the Known Issues section in the Wands for Oracle product release notes for further details.

  2. Restart the OACore JVM server.

  3. Load the Wands for Oracle test page to make the new version active. This is a simple web page that you access by entering the test page URL into a browser.

    1. Open a browser.

    2. Enter the URL for this Application server node followed by /OA_HTML/excel4apps e.g. http://appsserver1.domain.com:8000/OA_HTML/excel4apps

    3. The test page should display similar to the image below.

  1. If the APPL_TOP is not shared, repeat the process for the remaining nodes.

  2. For shared APPL_TOP installations just load test page for each Application server node URL to make the new version active for that node.

Upgrading from 5/6.x.x to 6.2.x and higher

Due to the change in Wands Launcher technology Autoconfig is required to be run for an upgrade to release 6.2.x.

Follow all steps outlined in section 3.3 Upgrading from 5.5.x and higher

Before step 10, please follow to these additional two steps.

  1. Run AutoConfig on the applications tier.

  2. Bounce the applications tier.

Upgrading from 6.2.x to 21.2.0 and higher

21.2.0 contains rebranding updates. For the rebranding of menus and responsibilities to run smoothly we recommend upgrading to this release using the hotpatch mode on the run file system. See section 3.3.2.

Installation on the Server

Pre-Install Steps

Follow these instructions in order to prepare the system for the installation and to deploy the install files:

  1. Locate the Wands for Oracle install file. This is the complete zip file that was downloaded from our web site (which contained this installation guide). FTP it to the server as the applications user.

  2. Unzip the Wands for Oracle install file.

  3. Initiate an adop prepare phase on the target installation environment.

  4. Connect to the Patch Edition file system on the target installation environment. Take careful note of the file system you are attached to as the steps below must be executed on the Patch Edition file system.

Setup the Excel4apps custom applications

This step explains the procedure to create the required custom Excel4apps applications by invoking the ADSplice utility from the Patch Edition file system. The instructions are based on the Oracle support note 1577707.1 - Creating a Custom Application in Oracle E-Business Suite Release 12.2 available on Oracle’s support website.

Run the ADSplice Utility

ADSplice is an Oracle utility that installs a product definition for new applications. It requires some configuration files which must first be prepared.

  1. As the Applications node technology stack owner (applmgr), navigate to the folder on the server where you unzipped the install file.

  2. Navigate to the Wands for Oracle install folder that will have been created by the unzip process earlier.

  3. For UNIX systems, change permissions on the file “install.sh” to allow it to be executed.

  4. Run the Wands for Oracle installer to deploy the ADSplice configuration files by running the install.sh script with the DEPLOY_ADSPLICE_FILES option as follows:

    UNIX:

./install.sh DEPLOY_ADSPLICE_FILES

Windows:

C:\>install.cmd DEPLOY_ADSPLICE_FILES

  1. Below is an example of the output that the installer will generate.

[applmgr@oracle122 wands_oracle21.1.0.0]$ ./install.sh DEPLOY_ADSPLICE_FILES

WARNING: Debug mode ON, log level=ALL

Installer Mode: DEPLOY_ADSPLICE_FILES

Wands for Oracle Installer Started

Enter the APPS username [APPS]: apps

Enter the APPS password:

Database Connection Details from Environment Context File:

/home/ebs122/oracle/VIS/fs1/inst/apps/VIS_oracle122/appl/admin/VIS_oracle122.xml

==========================================================

Server: oracle122

Port: 1525

Sid: VIS

Enter Y to use the following connection settings [Y]: Y

Enter Y to create custom tables in the APPS schema [N]: Y

Database Connection Details used for this installation: oracle122:1525:VIS

ADSPLICE Files Deployed Successfully

ADSPLICE Files Deployed Successfully

Installation completed successfully

Program Exit Status=0

[applmgr@oracle122 wands_oracle21.1.0.0]$

  1. Review the output from the Wands for Oracle Installer and proceed to run ADSplice below unless instructed otherwise.

  2. Change directory to the admin directory under $APPL_TOP and run the ADSplice utility as follows:

[applmgr@oracle122 admin]$ cd $APPL_TOP/admin

[applmgr@oracle122 admin]$ adsplice

  1. Respond to the application prompts and specifically accept the default values for the following items:

Enter the directory where your AD Splicer control file is located.

The default directory is [/oracle/VIS/apps/apps_st/appl/admin] :

Please enter the name of your AD Splicer control file [newprods.txt] :

Do you wish to regenerate your environment file [Yes] ?

  1. The ADSplice process will now run. When prompted to regenerate your environment file i.e. Run AutoConfig, please select Yes.

    1. Review the ADSplice log file to ensure the procedure completed successfully.

    2. Review the AutoConfig log file to ensure it completed successfully.

Verify the Excel4apps custom applications

  1. As the APPS user, connect to the patch edition database and run the following SQL to confirm that the applications were created successfully.

SELECT DECODE (foo.c, 1, 'Application XXE4A created', 'Error, application XXE4A was not created') answer

  FROM (SELECT COUNT (*) c

          FROM fnd_application fa, fnd_product_installations fpi, dba_users dau

         WHERE fa.application_short_name = 'XXE4A'

           AND fa.application_id = fpi.application_id

           AND dau.username = fa.application_short_name) foo

UNION ALL

SELECT DECODE (foo.c, 1, 'Application XXE4ARW created', 'Error, application XXE4ARW was not created') answer

  FROM (SELECT COUNT (*) c

          FROM fnd_application fa, fnd_product_installations fpi, dba_users dau

         WHERE fa.application_short_name = 'XXE4ARW'

           AND fa.application_id = fpi.application_id

           AND dau.username = fa.application_short_name) foo;

Note: You can use SQL*PLUS while accessing the patch edition file system to connect to the patch edition database.

  1. To ensure the new environment file is picked up, log out and then log back in again as the Applications node technology stack owner (applmgr). Source the Patch Edition file system and run the following command to confirm the $XXE4A_TOP is correctly set.

[applmgr@oracle122 ~]$ ls -l $XXE4A_TOP

total 24

drwxr-xr-x. 4 applmgr dba 4096 Oct 25 13:18 admin

drwxr-xr-x. 2 applmgr dba 4096 Oct 25 13:18 log

drwxr-xr-x. 2 applmgr dba 4096 Oct 25 13:18 mds

drwxr-xr-x. 2 applmgr dba 4096 Oct 25 13:18 mesg

drwxr-xr-x. 2 applmgr dba 4096 Oct 25 13:18 out

drwxr-xr-x. 2 applmgr dba 4096 Oct 25 13:18 sql

[applmgr@oracle122 ~]$

  1. Run the command above for the $XXE4ARW_TOP as well.

Excel4apps custom applications - Multiple Application Tier Nodes

  1. If the APPL_TOP is not shared, repeat the section “Setup the Excel4apps custom applications” for the remaining nodes.

  2. For shared APPL_TOP installations simply run AutoConfig for the remaining nodes. There is no need to rerun ADSplice.

Configure Allowed Resources

  1. For Oracle EBS 12.2.7 or 12.2.6 + Patch 24737426:R12.FND.C ensure that the “Allowed Resources” feature has been configured to grant access to the Wands for Oracle servlets. Refer to the Known Issues section in the Wands for Oracle product release notes for further details.

Install

This step involves running the Wands for Oracle Installer which will deploy the Wands for Oracle files on the server, configure the Wands for Oracle applet, load the Wands for Oracle OAF home page and load the required application components e.g. the menu and responsibility.

Note: An option to install custom database tables has been included in the installer. Please see the Custom Database Objects section of this guide to understand the implications.

  1. As the Applications node technology stack owner (applmgr), navigate to the folder on the server where you unzipped the install file.

  2. Navigate to the Wands for Oracle install folder that will have been created by the unzip process earlier.

  3. For UNIX systems, change permissions on the file “install.sh” to allow it to be executed.

  4. Ensure that you are still in the Patch Edition file system.

  5. Run the Wands for Oracle Installer

UNIX:

./install.sh

Windows:

C:\>install.cmd

  1. Below is an example of the output that the installer will generate.

[applmgr@oracle122 wands_oracle21.1.0.0]$ source /home/ebs122/oracle/VIS/EBSapps.env patch

  E-Business Suite Environment Information

  ----------------------------------------

  RUN File System : /home/ebs122/oracle/VIS/fs2/EBSapps/appl

  PATCH File System : /home/ebs122/oracle/VIS/fs1/EBSapps/appl

  Non-Editioned File System : /home/ebs122/oracle/VIS/fs_ne

  DB Host: oracle122.excel4apps.com  Service/SID: VIS

  Sourcing the PATCH File System ...

[applmgr@oracle122 wands_oracle21.1.0.0]$ ./install.sh

Installer Mode: DB_AND_APPS_TIER

Wands for Oracle Installer Started

Enter the APPS username [APPS]:

Enter the APPS password:

Database Connection Details from Environment Context File:

/home/ebs122/oracle/VIS/fs2/inst/apps/VIS_oracle122/appl/admin/VIS_oracle122.xml

==========================================================

Server: oracle122

Port: 1525

Sid: VIS

Enter Y to use the following connection settings [Y]:

Enter Y to create custom tables in the APPS schema [N]:

Database Connection Details used for this installation: oracle122:1525:VIS

Servlet Configured Successfully

Files Deployed Successfully

OAF Pages Loaded Successfully

APPS Components Created Successfully

ADOP Custom Synchronization Driver File Updated Successfully

Customer Tables Created Successfully

Installer completed successfully

Program Exit Status=0

[applmgr@oracle122 wands_oracle21.1.0.0]$

Run the adcgnjar Utility

The custom code must be packaged into a JAR file which is done using the adcgnjar utility.

  1. As the Applications node technology stack owner (applmgr)user run the adcgnjar Utility:

[applmgr@oracle122 classes]$ adcgnjar

  1. Enter the APPS username and password when prompted.

  2. The script has completed successfully when the following message is displayed:

customall.jar generated successfully.

Installation - Multiple Application Tier Nodes

  1. If the APPL_TOP is not shared, start a “nodb” adop patch cycle on the remaining Application Nodes and repeat the install. Please note that when running the Wands for Oracle Installer on additional nodes you should use the APPS_TIER option. This will ensure that only the application tier components are deployed and the database components are not redeployed with each run.

  2. Run the Wands for Oracle Installer with the APPS_TIER option.

UNIX:

./install.sh APPS_TIER

Windows:

C:\>install.cmd APPS_TIER

  1. Below is an example of the output that the installer will generate

[applmgr@oracle122 wands_oracle21.1.0.0]$ ./install.sh APPS_TIER

Installer Mode: APPS_TIER

Wands for Oracle Installer Started

Servlet Configured Successfully

Files Deployed Successfully

ADOP Custom Synchronization Driver File Updated Successfully

Installation completed successfully

Program Exit Status=0

[applmgr@oracle122 wands_oracle21.1.0.0]$

  1. For shared APPL_TOP installations, simply run AutoConfig for the remaining nodes.

Cutover

  1. Connect to the Run Edition file system and run the adop cutover phase.

Log on for the first time

  1. The installation process would have created the special Wands for Oracle responsibility. Log on to Oracle and assign the Wands for Oracle Responsibility to your Oracle user.

  2. Log out of Oracle and close all browser windows.

  3. Log on to Oracle in a fresh browser session using the user that you assigned the Wands for Oracle Responsibility to.

  4. You will be requested to install a browser dependent plugin. Please see the Wands Launcher section of the online user guide for all supported browser plugin instructions. The launch process will load the Wands for Oracle toolbar into Microsoft Excel.

  5. Request or enter a license key.

    • You may be prompted to request a license key or enter one received previously.

    • Additional details on requesting and entering license keys can be found in the Administrator section of the online user guide under the “System Administrator Options” section guide (accessible via the product or logging on to the customer community).

  6. Configure system administrator options.

    • Required settings: The first time you log on you must flag one (or more) Oracle user as a Wands system administrator(s). Once the license key is entered and saved, only this user(s) will have permissions to administer the installation, change options and set permissions for other users.

  7. Proceed to the product specific installation steps set out below.

Product Specific Installation Steps

There are some steps that need to be performed to enable functionality in specific products. These are set out below.

Shared Templates Drive

The System Administrator Configuration Options section of the online user guide (accessible via the product or logging on to the customer community) includes settings that affect the Shared Templates Drive functionality. If you wish to use the EBS Database option as your preferred Drive type, you will be required to execute a SQL script, please see the Shared Templates Drive Type section of the online user guide for complete configuration instructions.

GL Wand

There is not much that needs to be done specifically for the GL Wand product. You should just review the default options to ensure that they are appropriate for your users. These options can be set on the System Administrator options dialog. Please see the user guide (accessible via the product or logging on to the customer community) and navigate to the System Administrator Options section under the Wands (Oracle) menu and specifically review the System Administrator User Options which include a number of items that affect GL Wand functionality.

Report Distribution Manager (RDM)

The System Administrator User Options section of the online user guide (accessible via the product or logging on to the customer community) includes settings for configuring your email which will allow you to send RDM published workbooks via email.

Budget Wand

The System Administrator User Options section of the online user guide (accessible via the product or logging on to the customer community) includes settings that affect the Budget Wand functionality. In addition, should you wish to use the automatic posting feature for budget journals, you must complete the necessary setup of the AutoPost criteria set in Oracle. The details can be found in the user guide under the Budget Wand section.

Reports Wand

The Reports Wand product will work without any further configuration steps and you can create your own queries and reports. However, if you have the Reports Wand insights feature installed, you will need to enable it. The insights section of the of the online user guide include all instructions required for installing Reports Wand insights and generating all relevant content. Additional Reports Wand configuration options are detailed in the System Administrator User Options section of the online user guide.

Journal Wand

The System Administrator User Options section of the online user guide (accessible via the product or logging on to the customer community) includes settings that affect the Journal Wand functionality. In addition, should you wish to use the automatic posting feature for journals, you must complete the necessary setup of the AutoPost criteria set in Oracle. The details can be found in the user guide under the Journal Wand section.

Java Runtime Image

Wands applications are still a Java based application; however, it runs on a Java Runtime Image which is a stripped-down version of the OpenJDK and embedded into our codebase. This allows us to ship an Excel4apps version of Java with a release and removes the prerequisite of having Java installed on a client machine. This image is built from the latest version of OpenJDK to incorporate all the latest security fixes.

After logging into Oracle E-Business Suite, users can navigate to the Wands launch page causing the Wands Launcher plugin to kick off some commands, ensuring that the user has the latest copy of the Excel4apps client code. If the user does not have the latest, then they will be notified that the files are being updated. This downloads a new Java Runtime Image from the EBS server. This file is about 25mb and can impact the product launch on slower network speeds.

Custom Database Objects

The following features are dependent on custom database objects. The installer allows for the custom database objects to be automatically created in the APPS schema with default database settings.

Feature

Object Name

Object Type

Reports Wand insights

XXE4A_REPORT_DEFINITIONS

Database table

Reports Wand insights

XXE4A_REPORT_DEFINITIONS_TL

Database table

Reports Wand insights

XXE4A_REPORT_DEFN_COLUMNS

Database table

Reports Wand insights

XXE4A_REPORT_DEFN_COLUMNS_TL

Database table

GL Wand Report Wizard

XXE4A_CRITERIA_TEMPLATES

Database table

Shared Templates Drive

XXE4A_SHARED_TEMPLATES

Database Table

Report Usage Statistics

XXE4A_USAGE_STATS

Database Table

Report Usage Statistics

XXE4A_USAGE_STATS_SEQ

Sequence

Reports Wand Table Security

XXE4A_RW_TABLE_SECURITY

Database Table

Reports Wand Table Security

XXE4A_RW_TABLE_SECURITY_SEQ

Sequence

Multi Data Source

XXE4A_RW_MDS_CONNECTIONS

Database Table

 

The installer will prompt the user to install the custom database objects:

Enter Y to create custom tables in the APPS schema [N]: Y

The follow options are valid:

  1. Y – will only create database objects if they do not already exist.

  2. N – will not create any of the custom database objects.

  3. F – will remove existing database objects and recreate as new. This option will delete any data in the database tables.

It is important that you understand your current Oracle license agreement and whether custom database objects are permitted. The custom database objects can be installed after the installation should you not wish to install them at this point. All scripts for creation of the custom database objects are available in the online user guide under the relevant feature section.

Server Test Page

If required, you can test the server installation by loading the test page. The automated installation process will execute this step, but if you need to load the test page manually for any reason, proceed as follows:

  1. Open a browser.

  2. Enter the URL for your Oracle system followed by /OA_HTML/excel4apps e.g. http://server.domain.com:8000/OA_HTML/excel4apps.

  3. The test page should display similar to the image below.

Installation on the Client

On initial launch of this version, the user will be instructed to download and install the Wands Launcher. This will allow Wands to be launched from the browser.

Installation Troubleshooting

You can validate your Wands for Oracle installation at any time by executing the installer in VALIDATE mode. The installer will confirm if the required application components have been deployed and the necessary system configuration performed.

Run the Wands for Oracle Installer in VALIDATION mode, using the –-hotpatch option when executing in the RUN edition filesystem:

UNIX:

./install.sh --hotpatch VALIDATE

Windows:

C:\>install.cmd --hotpatch VALIDATE

Below is an example of the output that the validation routine will generate:

[applmgr@oracle122 wands_oracle21.1.0.0]$ ./install.sh --hotpatch VALIDATE

Installer Mode: VALIDATE

Wands for Oracle Installer Started

Enter the APPS username [APPS]:

Enter the APPS password:

Database Connection Details from Environment Context File:

/home/ebs122/oracle/VIS/fs2/inst/apps/VIS_oracle122/appl/admin/VIS_oracle122.xml

==========================================================

Server: oracle122

Port: 1525

Sid: VIS

Enter Y to use the following connection settings [Y]:

Servlet Configuration: PASSED

Application File Deployment: PASSED

OAF Artifacts: PASSED

AOL Objects: PASSED

Call Servlet Test Page: PASSED

Installer Completed Successfully

Program Exit Status=0

[applmgr@oracle122 wands_oracle21.1.0.0]$

If the installer validation routine fails, please contact Wands support by emailing the validation log file to e4asupport@insightsoftware.com.

Uninstall Steps

The following instructions can be used to uninstall the Wands for Oracle software on Oracle EBS 12.2.x environments:

  1. Shutdown all the application tier services.

  2. On both the Run and Patch Edition filesystems, remove the following folders on all Application Tier nodes where the installation was performed:

    1. $JAVA_TOP/com/excel4apps

    2. $APPL_TOP/xxe4a

    3. $APPL_TOP/xxe4arw

  3. Run the adcgnjar utility to recreate the customall.jar file, for example:

[applmgr@oracle122 classes]$ adcgnjar

  1. On both the Run and Patch Edition filesystems, remove the following lines from the bottom of the custom OACORE web.xml template file, $FND_TOP/admin/template/custom/oacore_web_xml_FMW.tmp :

<!-- Excel4apps Wands x Alias -->

<servlet>

<servlet-name>excel4apps</servlet-name>

<servlet-class>com.excel4apps.servlet.wand.oracle.Servlet</servlet-class>

</servlet>

<servlet-mapping>

<servlet-name>excel4apps</servlet-name>

<url-pattern>/excel4apps</url-pattern>

</servlet-mapping>

  1. End Date the Wands for Oracle Responsibility: Wands for Oracle

  2. Execute AutoConfig on the Run Edition Filesystem for all Application Tier nodes where the installation was performed.

  3. Remove the following entries from the $APPL_TOP_NE/ad/custom/adop_sync.drv file:

rsync -zr %s_current_base%/EBSapps/appl/xxe4a %s_other_base%/EBSapps/appl

rsync -zr %s_current_base%/EBSapps/appl/xxe4arw %s_other_base%/EBSapps/appl

rsync -zr %s_current_base%/EBSapps/appl/fnd/12.0.0/admin/template/custom %s_other_base%/EBSapps/appl/fnd/12.0.0/admin/template

cp %s_current_base%/EBSapps/comn/java/classes/customall.jar %s_other_base%/EBSapps/comn/java/classes

mkdir -p %s_other_base%/EBSapps/comn/java/classes/com/excel4apps

rsync -zr %s_current_base%/EBSapps/comn/java/classes/com/excel4apps %s_other_base%/EBSapps/comn/java/classes/com

  1. Start the application tier services.

Note: The Oracle E-Business Suite system does not allow for the complete removal of all custom configuration e.g. Custom Applications and is thus not covered by this procedure.

Other Topics and Performance Optimization

Please see the “Installation Guide - Other Topics” for details on customizing the launch configuration, downgrading to an older release, removing GL Wand 4, creating the Shared Templates Drive database table and more.

See the “Installation Guide - Performance Optimization” for our performance tuning tips.

Was this article helpful?

We're sorry to hear that.