0% found this document useful (0 votes)
159 views3 pages

Deployment Steps

1. Extract the zip file into the Java top directory and import two XML pages using the XMLImporter tool. 2. Backup the existing customall.jar file, run the adcgnjar tool to generate a new customall.jar, and bounce the weblogic server to deploy changes. 3. Download a new form function from the development environment and upload it to the target server, then assign it to the appropriate responsibility menu to make the new page accessible.

Uploaded by

mahesh84psg
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
159 views3 pages

Deployment Steps

1. Extract the zip file into the Java top directory and import two XML pages using the XMLImporter tool. 2. Backup the existing customall.jar file, run the adcgnjar tool to generate a new customall.jar, and bounce the weblogic server to deploy changes. 3. Download a new form function from the development environment and upload it to the target server, then assign it to the appropriate responsibility menu to make the new page accessible.

Uploaded by

mahesh84psg
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Deployment steps:

1. Move the zip file into $JAVA_TOP and extract it. After extraction, the folder
structure should be $JAVA_TOP/xxdfc/oracle/apps/per/eit... and so on...
2. Run the following command from command prompt of the server computer. Make sure
the environment has already been initialized for EBS commands. The following
command will import the page view component (xml file) into MDS tables.

java oracle.jrad.tools.xml.importer.XMLImporter %JAVA_TOP


%/xxdfc/oracle/apps/per/eit/webui/eitSelfServicePG.xml -username <apps_username>
-password <apps _pwd> -dbconnection "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=
<name of HOST>)(PORT=<port_number>))(CONNECT_DATA=(SID=<SID_NAME>)))" -rootdir
%JAVA_TOP%

java oracle.jrad.tools.xml.importer.XMLImporter %JAVA_TOP


%/xxdfc/oracle/apps/per/eit/webui/xxdfcAxnHistoryRN.xml -username <apps_username>
-password <apps _pwd> -dbconnection "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=
<name of HOST>)(PORT=<port_number>))(CONNECT_DATA=(SID=<SID_NAME>)))" -rootdir
%JAVA_TOP%

3. Print the uploaded page Document imported XML page content (Optional) to check
if the page has imported correctly ( from Toad/sqldeveloper/ sqlplus)

set serveroutput on;


begin

jdr_utils.printDocument('/xxdfc/oracle/apps/per/eit/webui/eitSelfServicePG');

end;
set serveroutput off;

4. Print the uploaded page Document imported XML region (Optional) to check if the
page has imported correctly ( from Toad/sqldeveloper/ sqlplus)

set serveroutput on;


begin

jdr_utils.printDocument('/xxdfc/oracle/apps/per/eit/webui/xxdfcAxnHistoryRN');

end;
set serveroutput off;

5. Navigate to $JAVA_TOP and rename the current customall.jar to


customall_bak_<deployment_date>.jar for back-up. Running adcgnjar utility will
replace the customall.jar file in $JAVA_TOP. Any errors during creation of
the file( for example during signing of the jar file ) will cause standard pages
not to work properly. In case of any erors while running the following command,
please rename the backup file customall_bak_<deployment_date>.jar to
customall.jar.

Run the command adcgnjar from $JAVA_TOP location. Provide the apps user
credentials when the program prompts for it. Wait for the program to complete and
check if customall.jar file has been created successfully. If there is any error,
please rename the back up file to customall.jar as mentioned above.
6. Navigate to $ADMIN_SCRIPTS_HOME and run the following commands to bounce the
weblogic server.

.\admanagedsrvctl.sh stop oacore_server1


Give weblogic pwd

.\admanagedsrvctl.sh start oacore_server1


Give weblogic pwd

Note: A new function 'XXDFCGOVTXNSS' has been created to access this OAF Page and
assigned to the Menu 'DFC Government Relations Self Service' of DFC Government
Relations Self Service Responsibility. After deployment the page can be accessed
from DFC Government Relations Self Service Responsibility under the name, 'DFC Govt
Transactions EIT Search'. Please follow the steps below if the page is deployed
into apps servers other than DEV and skip if the page is deployed into DEV.

7. Navigate to the preferred location to download the file. Download the form
function XXDFCGOVTXNSS from the DEV server using the following command.

FNDLOAD <apps_username>/<apps_pwd> 0 Y DOWNLOAD


$FND_TOP\patch\115\import\afsload.lct XXDFCGOVTXNSS.ldt FUNCTION
FUNCTION_NAME="XXDFCGOVTXNSS"

8. Move the file XXDFCGOVTXNSS.ldt from the downloaded location from the host
server to a preferred location in the target server.
9. From the location in target server where the XXDFCGOVTXNSS.ldt has been moved
into, run the following command to upload the form function into the system.

FNDLOAD <apps_username>/<apps_pwd> 0 Y UPLOAD


$FND_TOP\patch\115\import\afsload.lct XXDFCGOVTXNSS.ldt -WARNING=YES
UPLOAD_MODE=REPLACE CUSTOM_MODE=FORCE

After uploading the form function into the target server, assign it to the menu of
a preferred responsibility using the following steps:

10. Navigate to the System Administrator Responsibility -> Security ->


Responsibility -> Define.

Enter into Query mode in the Responsibility and query up the responsibility
to assign the form function to (for eg., 'DFC Government Relations Self Service
Responsibility'9 and note down the menu associated with the responsibility (for
eg., 'DFC Government Relations Self Service')

11. Navigate to System Administrator Responsibility -> Application -> Function, to


check if the required form function has been uploaded succesfully into the system.
Enter into query mode in the Function window and query up the function
XXDFCGOVTXNSS from the Function field in the Description tab. Note down the value
of the User Function Name (for eg.,'DFC Government Transaction EIT Search')

12. Navigate to System Administrator Responsibility -> Application -> Menu ->
Define. Query up the menu of the responsbility the form function is to be assigned
to. Add a new row to the list of functions available under the responsibility and
give appropriate SEQ Number, Prompt (for eg., DFC Govt Transactions EIT Search) and
Function ( select the User function name, for eg., DFC Government Transaction EIT
Search from LOV) and save the transaction. Now the OAF page is accessible from the
assigned Responsibility.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy