Considerations for Oracle EBS Form Publishing to server side

Some time ago on the local XP system to test some of the integration of JavaBean form example, want to publish to the server segment to see if it works properly, at first think it will be the same as the local XP system, deploy to the relevant directory to do some configuration, but the actual process is very different from the imagination, Deploying to a server can be called twists. The following are some considerations for publishing Oracle EBS Form to the server side:

1. Determine the EBS version

Because there are some differences in the location of the different versions of the EBS configuration jar file and the release JavaBean jar package, you must know the EBS version so that you have a problem to search for the corresponding solution. You can view the EBS version on the server by Sqlplus connecting to the EBS database:

1Sql*Plus:release10.1.0.4.2 -Production onTuesday November -  One:Ten: $  -2Copyright (c)1982,2005, Oracle. Allrights reserved.3 Connect to:4OracleDatabase11g Enterprise Edition Release11.1.0.7.0 -64bitProduction5  withThe partitioning, OLAP, Data Mining and RealApplication Testing Options6Sql> SelectRelease_name fromfnd_product_groups;7 Release_name8 --------------------------------------------------------------------------------9 12.1.1TenSql> 

You can see that the local version is 12.1.1.

2. Determine the operating system of the server

It is understood that EBS on different operating systems, JavaBean jar package configuration and upload directory also there are some differences, such as my local environment is XP, the server is Linux (Redhat), configuration environment is not the same, It's also why I started installing local configuration and always can't find the corresponding JavaBean jar package. The XP (Windows) system uploads the jar package to the location/forms/java/, and the configuration file is form/server/formsweb.cfg. but Linux is APPSWEB.CFG!!!

3. Determine deployment location

The server to be released is the Linux operating system and the EBS version is 12.1.1. The appsweb.cfg in Oracle EBS has two locations, namely:

1. $OA _html/bin and (This configuration file is for R11)
2. $ORA _config_home/10.1.2/forms/server/(This configuration file is for R12)

Enter a command at the terminal of the server to view the actual directory of the $ora_config_home/10.1.2/forms/server/, and then edit the appsweb.cfg in its directory

1 [[email protected] ~]$ $ORA _config_home/10.1. 2/forms/server/2 -bash:/u01/oracle/vis/inst/apps/vis_erp/ora/10.1. 2/forms/server/: is a director3 [[email protected] ~]$

Locate the archive node in appsweb.cfg (you need to append Javahost.jar =>/oa_java/oracle/apps/fnd/jar/javahost.jar, note that it is comma delimited):

archive=/oa_java/oracle/apps/fnd/jar/fndforms.jar,/oa_java/oracle/apps/fnd/jar/fndformsi18n.jar,/oa_java/ oracle/apps/fnd/jar/fndewt.jar,/oa_java/oracle/apps/fnd/jar/fndswing.jar,/oa_java/oracle/apps/fnd/jar/ fndbalishare.jar,/oa_java/oracle/apps/fnd/jar/fndaol.jar,/oa_java/oracle/apps/fnd/jar/fndctx.jar,/oa_java/ Oracle/apps/fnd/jar/javahost.jar
Here see Oa_java as the virtual directory, to the terminal to see its actual directory as:

1 [[email protected] ~]$ $OA _java/oracle/apps/fnd/jar/2 -bash:/u01/oracle/vis/apps/apps_st/comn/ java/classes/oracle/apps/fnd/jar/: is a3  directory4 [[email protected] ~]$

So upload Javahost.jar to/u01/oracle/vis/apps/apps_st/comn/java/classes/oracle/apps/fnd/jar/, this and $common_top/java/ Classes/oracle/apps/fnd/jar consistent.

1 [[email protected] ~]$  $COMMON _top/java/classes/oracle/apps/fnd/jar2 -bash:/u01/ oracle/vis/apps/apps_st/comn/java/classes/oracle/apps/fnd/Jar:is a3directory4 [email protected] ~]$

At this point, the deployment to the server file upload and configuration work is completed, and then upload the form to the corresponding directory, the configuration menu (the client and the server's SSH tool for bitvise ssh).

4. Other

To enable a process when opening the JavaBean form, open the URL: (Apple system with open) cmd/c start www.baidu.com?uid=username^&pwd=pwd (here ^ can be escaped & symbols)

The Execute button when-button-pressed trigger code is:

1: BL. RESULT:= "' ;2 --set_custom_property (' BL. BEAN ', 1, ' Set_prog ',: BL. CMD);3 --Use ^ to escape & in teh command line like this:4Set_custom_property ('BL. BEAN',1,'Set_prog','cmd/c start www.microstarsoft.com?uid=username__pwd^&pwd=2') ;

The user clicks are then simulated with code, and the button event is triggered when the form is activated (when-window-activated):

1 -- automatically perform click events 2 -- go_item (' <block_name>.<button_name> '); 3 -- Execute_trigger (' when-button-pressed '); 4 go_item ('BL. EXECUTE'); 5 Execute_trigger ('when-button-pressed');

By default, after the Oracle form loads, clicking the Close button is not valid under Key-exit of the form:

1

　　

Considerations for Oracle EBS Form Publishing to server side