Wands (Oracle) 5.10 : Custom Options

This procedure explains how to configure custom options for the Excel4apps Wands. These are special options that need to be set before the application launches and therefore cannot maintained through the user interface in Excel. They are instead maintained in a properties files stored on the Oracle server.

Currently only one custom option exists which is the CUSTOM_LIBRARY_OUTPUT_FILE_PATH option. It controls where the Excel4apps libraries are extracted to on the PC when the application is launched.

CUSTOM_LIBRARY_OUTPUT_FILE_PATH

To configure the custom library output file path option, proceed as follows:

1. Navigate on the server to the $JAVA_TOP/com/excel4apps/applet folder.
2. In that folder you will find a file called e4awand_oracle_custom_options.template
3. Copy this file and name it e4awand_oracle_custom_options.properties.
4. Open the properties file to edit it.
5. The file will contain 1 entry - CUSTOM_LIBRARY_OUTPUT_FILE_PATH=DEFAULT
6. Edit this entry to point to a custom folder for the Excel4apps libraries:
   1. You specify the full absolute path e.g. C:\Program Files (x86)\Excel4apps
   2. Due to the syntax requirements, each \ must be duplicated e.g. C:\\Program Files (x86)\\Excel4apps
   3. Make sure that the folder you point to has write permissions for all users.
   4. The same path will be used for all users and therefore must exist on all PCs where the Excel4apps Wands will be used.
   5. If the complete path specified does not exist, the application will attempt to create it. This will be fine as long as the user executing the application has write permissions to that folder path.
   6. Save the file.
7. If you are using Oracle 12.2, there are additional steps required. Continue with these instructions at the end of this page.
8. Launch the application. The Excel4apps libraries should now be extracted to the folder specified.

See the screenshots below for an example:

Additional Steps - Oracle 12.2

1. The initial steps set out above should be completed on the Run Edition file system.
2. Once the properties file has been created and edited, the custom code must be packaged into a JAR file which is done using the adcgnjar utility.
3. As the Applications node technology stack owner (applmgr) user run the adcgnjar Utility:

   1. adcgnjar

4. Enter the APPS username and password when prompted.

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

   1. customall.jar generated successfully.