4 Configuring a Standalone Application Server

4.1 Installation Overview

• Install and start the database

• Install JDK for 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 12.1.3, 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.

To install Oracle Fusion Middleware Infrastructure 12.1.3:

1. Copy the fmw_12.1.3.0.0_infrastructure.jar file from the Agile PLM Media Pack to your machine.

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.1.3.0.0_instrastructure.jar.

4. Click Next.

5. Enter the path where you want to install Oracle Fusion Middleware Infrastructure. Make a note of this location because it will be needed 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: Before running the Repository Creation Utility, apply the following patch to the Oracle Fusion Middleware 12.1.3 ORACLE_HOME: Patch 19614859—OPSS RCU throws three ORA-1450 errors when using CHAR semantics database If this step is not performed and you are creating the RCU schemas in a CHAR semantics (i.e. NLS_LENGTH_SEMANTICS=CHAR) database then you will get ORA-01450 errors indicating that the maximum key length was exceeded during creation of three indexes in the OPSS schema. If this occurs, you must run RCU and drop the repository, run RCU again, and recreate the repository so that it completes without errors.

Note: The Agile PLM application server installation 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 required schemas using RCU:

1. In a command window, change to the directory, ORACLE_HOME\oracle_common\bin. ORACLE_HOME is where Oracle Fusion Middleware Infrastructure 12.1.3 is installed.

2. Run the following command:

3. • Windows: rcu.bat

   • UNIX: ./rcu

4. On the Welcome page, click Next.

5. On the Create Repository page, choose System Load and Product Load, then click Next.

6. 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.

7. On the Select Components page, enter a prefix for all schemas to be created. 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 will be needed during the Agile PLM installation.

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

9. • Metadata Services

   • Audit Services

   • Audit Services Append

   • Audit Services Viewer

   • Oracle Platform Security Services

   • Common Infrastructure Services (selected by default)

10. Click Next.

11. On the Schema Passwords page, enter the password that should be used for all schemas. You can also enter different passwords for each schema, if you prefer. Click Next.

12. On the Map Tablespaces page, a table of default and temp tablespaces is displayed. Click Next.

13. 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: When installing the Agile PLM application server component, you must select the same JDK used to install the Oracle Fusion Middleware Infrastructure software.

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

It is recommended to back 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.

See the Agile Product Lifecycle Management Web Services Guide for information and instructions on how to enable and disable WSS.

4.5 Starting and Testing the Agile PLM Application Server Connection

After you have installed and started 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 Agile PLM Application Server and test the connection:

1. Start the Agile Application Server.

   Windows service: Start the Windows service AgilePLM.

   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 may appear and this window must remain open but can be minimized.

   UNIX command line: Run the startAgile.sh script located in the AGILE_HOME/agileDomain/bin directory.

   Wait until the following message appears in the command window or application server log file before connecting: "Agile PLM Server Starting Up".

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 window appears.

3. Enter the username and password.

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

   The first time you log in to the application, it may take a while to load the information.