Scribd Logo
Upload

Welcome to Scribd!

  • 25 views

    Configure Deploy OrgChartApplication Ear

    Uploaded by

    Abhishek Singh Tomar

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Configure Deploy OrgChartApplication Ear

    Uploaded by

    Abhishek Singh Tomar
    25 views8 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    25 views8 pages

    Configure Deploy OrgChartApplication Ear

    Uploaded by

    Abhishek Singh Tomar

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 8

    Configuring and Deploying Organization Chart

    An Oracle White Paper


    June 2015
    This document covers the steps to configure and deploy the Organization Chart feature.

    Section 1: Prerequisite Patches for Oracle E-Business Suite


    Instance
    Ensure that the following profiles are available in your system:

    1. FND_SERVER_SEC

    2. FND_SERVER_IP_SEC

    3. FND_SERVER_DESKTOP_USER

    If these profile options do not exist in your system, then apply Patch 12715586 SEEDING
    MISSING FND_SERVER* PROFILES INTO R12 (compatible with R12.FND.B). Note that
    AOLJ patch#12715586 is EBS mid-tier patch and is release dependent.

    If these profile options exist in your system, then there is no need to apply the patch.

    1.2. Instructions for extracting fndext.jar


    1. Download the patch for Organization Chart mentioned in the Document ID: 1408355.1 from
    My Oracle Support. Unzip the patch zip file. The zip file contains per_orgchart.zip,
    which contains file
    o OrgChartApplication.ear
    o Unzip OrgChartApplication.ear and extract the fndext.jar file
    2. Copy the extracted fndext.jar file to a directory such as /tmp/work/ on the WebLogic
    server machine.
    3. This fndext.jar would be used for the below configurations.

    Section 2: Using Oracle E-Business Suite Data Sources:


    AppsDataSource
    Please refer to the My Oracle Support Note 974949.1 for details about the AppsDataSource and
    on how to configure it in the chapter “Using Oracle E-Business Suite DataSources”. The
    sections that are to be followed from the note for this chapter are as follows

    2.1.2. Register the External Node and Generate the Desktop DBC File
    2.1.3. Set Up Necessary Oracle E-Business Suite Users
    2.1.5. Configuring AppsDataSource on Oracle WebLogic Server (WLS)

    For rebuilding the fndext.jar for the Oracle WebLogic server, use the fndext.jar got from
    step 1.2 (Instructions for extracting fndext.jar) from this document and do not use the
    fndext.jar from the patch specified in the note. Rebuilding jar step is NOT mandatory or
    required if you are using this jar for AppsDataSource feature. This step is mandatory for
    EBS JAAS feature delivered through fndext.jar.

    In step 2.1.5.4 Configure the Data Source in the Administration Console, use the
    following values instead of the values specified in the note. For other instructions, please
    follow from the note.

    1. Name for the datasource: AppsDS


    2. JNDI Name: jdbc/AppsDS
    3. Database Type: Oracle
    4. Database Driver: "Oracle's Driver (Thin) for Instance connections; Versions:
    9.0.1,9.2.0,10,11.
    Note: For Organization Chart in Oracle SSHR, use non-XA data source and
    uncheck the Supports Global Transactions check box.

    Skip all the steps from the section 2.1.4 and 2.2 from the My Oracle Support Note 974949.1.

    Section 3: Changing ApplServerId of Plan.xml


    Note: You must supply the domain name i.e java oracle.apps.fnd.security.AdminDesktop <apps
    user>/<apps passwd> CREATE NODE_NAME=<WLS name>.<domain> IP_ADDRESS=<WLS IP ADDRESS>
    DBC=$FND_SECURE/<ENV>.dbc

    1. Get the value of APPL_SERVER_ID parameter from the desktop DBC file that is
    generated with oracle.apps.fnd.security.AdminDesktop executable. This parameter value
    ensures the trusted relationship between external application server and e-business
    instance.

    2. Log in to the Oracle WebLogic Server Administration Console and navigate to Domain
    Structure->Deployments and click the "Install" button.
    3. Enter the location of your application ear file, and then click "Next". (Screenshot shows
    example for our application war file)

    4. On the following screen, select "Install this deployment as an application", and click
    Next. Name the deployment and click the "Finish" button. The 'Successful deployment
    message' appears.

    5. Navigate to the Configuration tab, save your configuration as Plan.xml, and then click the
    "OK" button.
    6. You must manually edit this file to define configuration parameters for your application.
    The file will look like this (some values may be different on your system)
    <?xml version='1.0' encoding='UTF-8'?>
    <deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" ...>
    <application-name>OrgChartApplication</application-name>
    <module-override>
    <module-name>OrgChartApplication.ear</module-name>
    <module-type>ear</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-application</root-element>
    <uri>META-INF/weblogic-application.xml</uri>
    </module-descriptor>
    <module-descriptor external="false">
    <root-element>application</root-element>
    <uri>META-INF/application.xml</uri>
    </module-descriptor>
    <module-descriptor external="true">
    <root-element>wldf-resource</root-element>
    <uri>META-INF/weblogic-diagnostics.xml</uri>
    </module-descriptor>
    </module-override>
    <module-override>
    <module-name>OrgChart_ViewController_webapp1.war</module-name>
    <module-type>war</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-web-app</root-element>
    <uri>WEB-INF/weblogic.xml</uri>
    </module-descriptor>
    <module-descriptor external="false">
    <root-element>web-app</root-element>
    <uri>WEB-INF/web.xml</uri>
    </module-descriptor>
    </module-override>
    <config-root></config-root>
    </deployment-plan>

    7. You need to add similar XML after the first bold, highlighted line (<application-
    name>...</application-name>) for the application parameter APPL_SERVER_ID
    <variable-definition>
    <variable>
    <name>app_APPL_SERVER_ID</name>
    <value>[value of APPL_SERVER_ID in DBC file (Step 1)</value>
    </variable>
    </variable-definition>
    8. Add similar XML tag as shown below, after the second bold, highlighted line
    (<uri>WEBINF/web.xml</uri>) for application parameter APPL_SERVER_ID

    <variable-assignment>
    <name>app_APPL_SERVER_ID</name>
    <xpath>/web-app/context-param/[param-name="APPL_SERVER_ID"]/param-
    value</xpath>
    <operation>replace</operation>
    </variable-assignment>

    9. After editing the deployment plan xml file, you must redeploy the application with this
    modified plan. Return to the Oracle WebLogic Server Administration Console and navigate
    to Domain Structure -> Deployments, check the box corresponding to your deployed
    application , then click the "Update" button.

    10. Select "Redeploy this application using the following deployment files:", and make sure
    it shows your modified Plan.xml file. Click "Next".
    11. On the next screen, click the "Finish" button to complete the redeployment.
    Oracle Corporation
    World Headquarters
    500 Oracle Parkway
    Redwood Shores, CA 94065
    U.S.A.

    Worldwide Inquiries:
    Phone: +1.650.506.7000
    Fax: +1.650.506.7200
    www.oracle.com

    Oracle Corporation provides the software


    that powers the internet.

    Oracle is a registered trademark of Oracle Corporation. Various


    product and service names referenced herein may be trademarks
    of Oracle Corporation. All other product and service names
    mentioned may be trademarks of their respective owners.

    Copyright © 2012 Oracle Corporation


    All rights reserved.

    You might also like