Go to primary content
Agile Product Lifecycle Management Application Installation Guide
Release 9.3.6
E71159-06
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

4 Configuring a Standalone Application Server

4.1 Installation Overview

  • Install and start the database

  • Install JDK for the application server

  • Install Oracle Fusion Middleware Infrastructure (includes WebLogic Server)

  • Install Agile PLM application components: standalone application server and file manager.

4.2 Installing the Server JDK

The application server software for Agile PLM requires a 64-bit JDK be installed in order to perform the installation. Download and install a supported JDK from the downloads link on the Oracle Technology Network website.

4.3 Installing Oracle Fusion Middleware Infrastructure

The Agile PLM application server component requires that Oracle Fusion Middleware Infrastructure, which includes Oracle WebLogic Server, be installed before installing the Agile PLM application server component. The Oracle Fusion Middleware Infrastructure installer installs additional components including Java-required files, Oracle Web Services Manager, Oracle Enterprise Manager, and Oracle Platform Security Services.


Note:

Oracle Fusion Middleware 12c Infrastructure version 12.2.1.3 can be downloaded by logging into Oracle Software Delivery Cloud (https://edelivery.oracle.com), searching with the term "Oracle Fusion Middleware 12c Infrastructure" and choosing "REL: Oracle Fusion Middleware 12c Infrastructure 12.2.1.3.0".

To install Oracle Fusion Middleware Infrastructure 12.2.1.4

  1. Download the Oracle Fusion Middleware 12c Infrastructure version 12.2.1.3 distribution to your machine and extract its contents.

  2. Open a command window and set JAVA_HOME to the location of the previously installed JDK.

  3. Run the following command: %JAVA_HOME\bin\java -jar fmw_12.2.1.3.0_infrastructure.jar.

  4. Click Next.

  5. Type the path that you want to install the Oracle Fusion Middleware Infrastructure and make a note of this location because you will need it later during the installation.

  6. Click Next on all panels until Installation Summary.

  7. Click Finish to complete the installation.

4.4 Running the Repository Creation Utility

The Repository Creation Utility (RCU) creates database schemas required by Oracle Fusion Middleware Infrastructure. It must be run before installing the Agile PLM application server component.


Note:

Installing the Agile PLM application server requires fresh RCU schemas. If a previously installed environment is being reinstalled, then its associated RCU repository must be dropped and recreated before reinstalling Agile PLM.

To create the schemas using RCU:

  1. In a command window, change to the directory, ORACLE_HOME\oracle_common\bin. ORACLE_HOME is the location of the Oracle Fusion Middleware Infrastructure installation.

  2. Run the following commands for Windows and UNIX:

    • Windows: rcu.bat

    • UNIX: ./rcu

  3. On the Welcome page, click Next.

  4. On the Create Repository page, select System Load and Product Load and then click Next.

  5. On the Database Connection Details page, enter the RCU database connection information. You can use the Agile PLM database to host the RCU schemas. Click Next.

  6. On the Select Components page, type a prefix for schemas that you want to create. You should consider setting the RCU schema prefix to the Agile PLM schema name so it is clear with which Agile PLM schema the RCU schemas are associated. Make a note of the schema prefix or names because they are needed during Agile PLM installation.

  7. Select the following repository components under AS Common Schemas:

    • Metadata Services

    • Audit Services

    • Audit Services Append

    • Audit Services Viewer

    • Oracle Platform Security Services

    • Common Infrastructure Services (selected by default)

  8. Click Next.

  9. On the Schema Passwords page, type the password that should used for all schemas. You can also type different passwords for each schema.

  10. Click Next.

    A table of default and temp Tablespaces is displayed on the Map Tablespaces page.

  11. Click Next.

  12. Click Create to complete the RCU installation.

4.4.1 What to Do Next

Install Agile PLM and its components by starting the Agile PLM installer and following the instructions in online help.


Note:

Download and apply patch 27871474 to the Agile PLM 9.3.6 installer before installing Agile PLM. This patch allows Agile PLM 9.3.6 to be installed with FMW 12.2.1.3.


Note:

When installing the Agile PLM application server component, you must select the same JDK that you used to install the Oracle Fusion Middleware Infrastructure software.


Note:

If you are using the AutoVue Server, you must install AutoVue client libraries before deploying the application server and file managers. See the AutoVue for Agile PLM Installation and User Guide for instructions.

Oracle recommends backing up the <AGILE_HOME>\agileDomain\security folder after installation.

4.4.2 Enabling Web Services Security (Optional)

Agile PLM supports Web Services Security (WSS) for customers who want to configure additional protection for web services.

Refer to the Agile Product Lifecycle Management Security Guide for WSS related configuration information.

4.5 Starting and Testing the Agile PLM Application Server Connection

After installing and starting the Agile PLM Application Server, you can test the connection using the application server listen ports configured during installation.


Important:

It is important that you do not provide users with this URL. The port you specified during the Application Server installation may be non-standard and may not be appropriate for use by external or remote Agile Web clients. This URL is a direct connection to the Application Server, and it should be used only for testing the troubleshooting purposes.

To start the Agile PLM Application Server and test the connection:

  1. Start the Agile Application Server as follows:

    • On Windows Service, select Start >Services>AgilePLM.

    • On Windows command line, run the startAgile.cmd script, located in the AGILE_HOME\agileDomain\bin directory OR choose Start > All Programs > Agile > Agile PLM > Start Agile Server. A command window will appear and this window must remain open but you can minimize it.

    • On UNIX command line, run the startAgile.sh script located in the AGILE_HOME/agileDomain/bin directory.

      A message stating "Agile PLM Server Starting Up" appears in the command window or the application server log file before connection.


      Note:

      On IBM AIX, if the application server(s) fails to start with error "java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration" then use the following workaround:

      1] Shut down the application server(s).

      2] Open a terminal window and change to directory AGILE_HOME/agileDomain/applications

      3] Make a backup copy of file application.ear as follows: cp -pr application.ear application.ear-SAVE

      4] Set environment variable JAVA_HOME to the directory where the JDK was installed.

      5] Extract the file weblogic-application.xml from application.ear using the following command: $JAVA_HOME/bin/jar -xvf application.ear META-INF/weblogic-application.xml

      6] Edit file META-INF/weblogic-application.xml and delete the following line:

      <wls:package-name>org.apache.xerces.*</wls:package-name>

      7] Update file weblogic-application.xml in application.ear using the following command: $JAVA_HOME/bin/jar -uvf application.ear META-INF/weblogic-application.xml

      8] Delete any existing WebLogic cache directories under AGILE_HOME/agileDomain/servers and start the application server(s).


  2. Open your browser and use the following URL to test the Agile Web client setup:

    http://application_server_hostname:port/virtual_path/PLMServlet


    Note:

    The URL is case-sensitive. The default virtual_path is Agile.

    A login dialog appears.

  3. Type the username and password.

    You can log in with the built-in Administrator account by typing admin for the user and the password that you supplied for the admin user in the password management screen during installation.


    Note:

    The first time that you log in, it will take a few moments for the information to load.