Recording Agent for EBS 12.2 Follow

 

1. Copy the AuraPlayerAgent.jar file to the following directory:  

$OA_JAVA/oracle/apps/fnd/jar/

This is the same location as the fndforms.jar file would usually be found.

Example path:

/u01/install/VISION/fs1/EBSapps/comn/java/classes/oracle/apps/fnd/jar

In order to avoid security warnings, if you have other jar files in the Oracle environment that you signed  as part of your Oracle EBS deployment process, you must sign the AuraPlayerAgent.jar with the same certificate.

 

2. Copy the auraplayer.properties file to the following location:

/$OA_JAVA/

Example path:

/u01/install/VISION/fs1/EBSapps/comn/java/classes

 

3. Changes in System  Administrator->Profile : Create a User that would be the AuraPlayer's 'recording user'

This user would open the Form in recording mode for AuraPlayer.

Go to the System Profile Form, and change the profile EBS User that would be the recording user

Open the following form:  System Administrator->Profile->System

In the Profile enter: ICX%Forms%Launcher, enter the user name,  and click on Find:

Copy the Site's url, paste it into the User's url, and change the config from ?config=jws to  ?config=ap_browserMode

After those settings what we would have:

1. The 'default' site settings would be web (applet) - it would not be used.
2. When all users would open the Form it would open java web start (jws configuration)
3. In some cases, server configurations also should be set to ?config=jws (jws configuration)

3. There is a 'recording user' a user that when he opens a Form, the Form would be opened in applet, and in recording mode

 

4. Edit EBS Forms configuration file: appsweb.cfg file. The file can be found in the following location:

$FORMS_WEB_CONFIG_FILE

Example path:

/u01/install/VISION/fs1/int/apps/DEMO_localhost/ora/10.1.2/forms/server/appsweb.cfg

Changes in the File:

1. Backup existing appsweb.cfg file : cp appsweb.cfg cp appsweb.cfg.<date>
2. Edit appsweb.cfg file, and:
3. create a new config section: ap_browserMode.
4. Add the following parameters in addition to the ap_browserMode:
   • archive2=,AuraPlayerAgent.jar path
   • record=names
   • formsMessageListener=com.auraplayer.ListenerWS
   • copy baseHTML and baseHTMLJInitiator properties to this section, and rename the HTML file name on both from: appsbase.htm to ap_appsbase.htm

Example config:

[ap_browserMode]

archive2=,/OA_JAVA/oracle/apps/fnd/jar/AuraPlayerAgent.jar

formsMessageListener=com.auraplayer.ListenerWS

record=names

baseHTML=<path to appsbase.htm>/ap_appsbase.htm

baseHTMLJInitiator=<path to appsbase.htm>/ap_appsbase.htm

 

5. Create new HTML configuration file for Recording agent

a. In the appsweb.cfg file find the path of the appbase.htm file - in the baseHTML property 

Example path:

/u01/install/APPS/fs1/FMW_Home/Oracle_EBS-app1/applications/oacore/html/US/

 

b. Duplicate the file appsbase.html and name it as ap_appsbase.html. Edit the file, and add the following:

• • After the following line:

IEhtml += '<' + 'PARAM name=code          value="' + xcode     + '">';

Add:

IEhtml += '<PARAM name=formsMessageListener value="%formsMessageListener%">';

• • Then after the following line:

 NShtml += '    java_version="%sun_plugin_version%" ';

Add:

NShtml += ' formsMessageListener="%formsMessageListener%"';

 

 

6. Restart Apache service on EBS

cd $ADMIN_SCRIPTS_HOME
./adapcctl.sh stop
./adapcctl.sh start

 

7. Please note for security sake you will need to re-sign AuraPlayerAgent.jar with the same certificate that the EBS jars were signed with during installation.

For example: 

jarsigner -keystore $APPL_TOP/admin/adkeystore.dat AuraPlayerAgent.jar AuraPlayer

If  the signing of the jar files fails or if it is not possible to re-sign the jars you can work around the issue by changing the .java.policy file in the development client PC that will be  performing the creation of webservices using the AuraPlayer recording toolbar

 

8. (OPTIONAL - If you were unable to sign the jar files) Changing the java policy settings on the recording machine.

Instructions

 

9. Update the template file for autoconfig so the above changes would not be overridden during patch/reset of the EBS server

 

Troubleshooting:

 

What we got left to do in order to make sure that our settings would not be changed after autoconfig runs:

1. Run autoconfig and make sure that it does not override:

server profile - icx forms launcher - should be empty

site profile - icx forms launcher - should be config=jws

site profile - java web start enabled - should be Yes

 

2. We should set the appsweb template with the configurations that we want to have after the script generation:

add config section ap_browserMode - for recording user.

set record flag to be record=names in the default settings

add record= in the jws configuration