2 Understanding the Installation Pre-requisites

This chapter describes the procedure you must use to install the ADF 12c runtime and deploy the tool's EAR file. For more information about domain creation and other server related information, see the WebLogic application server documents.

Installation and Setup Instructions

This section describes the installation and setup instructions including the installation pre-requisites, preparing the WebLogic server, creating a WebLogic domain, verifying installation of ADF runtime libraries, extending an existing domain to add ADF runtime libraries, and deploying the EAR file. It also describes guidelines to set up security.

Note: The windows included in the following procedures are for example purposes only. Because these procedures must be followed for each application, valid values vary. Therefore, consider the illustrations as guides only; the values shown may not always apply.

Pre-requisites

JMS Console application requires Oracle WebLogic Server 12c (12.2.1), built with Java 8 (JDK 1.8 64 bit with the latest security updates).

Installing WebLogic with ADF Runtime

To get the ADF runtime option while creating the domain, install the Application Development Runtime. To obtain Application Development Runtime, go to the Oracle Technology Network and take the following steps:

1. Find fmw_12.2.1.0.0_infrastructure_Disk1_1of1.zip and download this file to your system.

2. Extract the contents of this zip file to your system. You will use the fmw_12.2.1.0.0_infrastructure.jar file to run the installer.

3. Run the installer by executing the jar file:

   java -jar fmw_12.2.1.0.0_infrastructure.jar

   The Welcome window displays.

   
   

4. Click Next. The Auto Updates window displays. Select the appropriate option.

   
   

5. Click Next. The Installation Location window displays. Click Browse to select the Oracle Home location where the WebLogic Server is to be installed.

   
   

6. Click Next. The Installation Type window displays. Select the type of installation.
   

7. Click Next. The installer performs the pre-requisite checks and ensures all required conditions are satisfied.

   
   

8. When the pre-requisite check completes successfully, click Next. The Security Updates window will display. Enter the information as required.
   

9. Click Next. The Installation Summary window displays.

   
   

10. Click Install. The Installation Progress window displays.

    
    

11. Click Next when the installation completes. The Installation Complete window displays.
    

Creating the Required Schema Using Repository Creation Utility

To create a schema user for the jms-console domain, take the following steps:

1. Run the RCU from the <MW_HOME>/oracle_common/bin folder. The Welcome window displays.
   

2. Click Next and select the Create Repository option.

   
   

3. Click Next. Enter the database credentials where the schema user has to be created.
   

4. Click Next. Specify the prefix to be used for the schema user creation. For example, INT. Select Metadata Services, Weblogic Services, and Oracle Platform Security Services.
   

5. Click Next. Specify the password.

   
   

6. Click Next. The window provides the details of tablespaces created as part of schema creation.
   

7. Click Next. The Confirmation window displays.

   
   

8. Click OK. The Summary window displays.

   
   

9. Click Create and proceed to create the schema. This could take a while to complete. The Summary window displays.
   

Creating a WebLogic Domain with ADF Runtime Libraries

To create a new WebLogic domain with ADF runtime libraries, take the following steps:

1. Run the config.sh from the <ORACLE_HOME>/oracle_common/common/bin folder. The Configuration Type window displays.
   

2. Select Create a new domain, provide domain location, and click Next. The Templates window displays. By default, the Basic WebLogic Server Domain - 12.2.1.0 [wlserver] check box is selected.

   Select the Oracle JRF - 12.2.1 [oracle_common], Oracle Enterprise Manager - 12.2.1 [em], Oracle WSM Policy Manager - 12.2.1.0 [oracle_common], and WebLogic Coherence Cluster Extension - 12.2.1[wlserver] check boxes.

   
   

3. Click Next. The Administrator Account window displays. Enter the user credentials you want to use to log in to the WebLogic Administration Console.
   

4. Click Next. The Domain Mode and JDK window displays. Set the Domain Mode as Production and select the JDK version (JDK 1.8 with the latest security updates) you want to use.

   
   

5. Click Next. The Database Configuration Type window displays.

   1. Select the RCU Data radio button.

   2. Select Oracle as the Vendor.

   3. Select Oracle's Driver (Thin) for Service connections; Version 9.0.1 and later as the Driver.

   4. Enter the Service, Host Name, Port, Schema Owner, and Schema Password for the *_STB schema created using the RCU.

   5. Click Get RCU Configuration.

      The Connection Result Log displays the connection status.

      
      

6. Click Next. The JDBC Component Schema window displays.

   
   

7. Click Next. The JDBC Component Schema Test window displays status on whether the JDBC tests on the schemas were successful.

   
   

8. Click Next. The Advanced Configuration window displays. Select all the checkboxes, except Domain Frontend Host Capture and JMS File Store options, in this window.
   

9. Click Next. The Administration Server window displays. Enter the Listen Address and the Listen Port details.

   
   

10. Click Next. The Node Manager window displays. Select the Node Manager Type and enter the Node Manager Credentials.

    
    

11. Click Next. The Managed Servers window displays.

    1. Click Add to add a managed server on which you will deploy JMS Console.

    2. Enter the Server Name, Listen Address, and Listen Port for the managed server.

    3. Set the Server Groups to JRF_MAN_SRV.

       
       

12. Click Next. The Clusters window displays.

    1. Click Add to add a cluster. This is an optional step in the procedure.
       

13. Click Next. The Coherence Clusters window displays.

    1. Add a coherence cluster. This is an optional step in the procedure.

       
       

14. Click Next. The Machines window displays.

    1. Click Add.

    2. Enter the Name and the Node Manager Listen Address for the managed server.

       
       

15. Click Next. The Assign Servers to Machines window displays. Add the Admin Server and the managed server to the computer.

    
    

16. Click Next. The Deployments Targeting window displays. Select wsm-pm from Deployments and add it to AdminServer in Targets.

    
    

17. Click Next. The Services Targeting window displays.

    
    

18. Click Next. The Configuration Summary window displays. Verify that all information described in this window is accurate.

    
    

19. Click Create. The Configuration Progress window displays a message when the domain is created successfully.

    
    

20. Click Next. The Configuration Success window displays that describes the Domain Location and Admin Server URL once the configuration is complete.

    
    

21. Click Finish to complete creating the WebLogic domain and managed servers with ADF runtime.

Verifying the Installation of the ADF Runtime Libraries

To verify the installation of the ADF runtime libraries, take the following steps:

1. Start the Admin Server in the WebLogic domain and log on to the WebLogic Server Administration console with the admin credentials.

2. In the Domain Structure section, click Deployments. The deployed libraries are listed.

   
   

3. Click on an ADF library and go to the Targets tab. Verify that the library is targeted to both the Admin Server and the managed server. Verify these details for all the ADF libraries.

   
   

Extending an Existing Domain to Add ADF Runtime Libraries

To extend an existing domain to add ADF runtime libraries, take the following steps:

1. Run config.sh from the <ORACLE_HOME> /oracle_common/common/bin folder. The Configuration Type window displays.

   
   

2. Select the Update an existing domain option. Click Browse and choose the location of the domain to be updated with the ADF libraries.

3. Click Next. The Templates window displays. Select the Oracle JRF - 12.2.1 [oracle_common],, Oracle Enterprise Manager - 12.2.1 [em], Oracle WSM Policy Manager - 12.2.1.0 [oracle_common], and WebLogic Coherence Cluster Extension - 12.2.1 [wlserver] checkboxes.

   
   

4. Click Next. The Database Configuration Type window displays.

   1. Select the RCU Data radio button.

   2. Select Oracle as the Vendor.

   3. Select Oracle's Driver (Thin) for Service connections; Version 9.0.1 and later as the Driver.

   4. Enter the Service, Host Name, Port, Schema Owner, and Schema Password for the *_STB schema created using the RCU.

   5. Click Get RCU Configuration.

      The Connection Result Log displays the connection status.

      
      

5. Click Next. The JDBC Component Schema window displays.

   
   

6. Click Next. The JDBC Component Schema Test window displays which indicates the status of the schema tests.

   
   

7. Click Next. The Advanced Configuration window displays. Select the Managed Servers, Clusters and Coherence and the Deployments and Services checkboxes.

   
   

8. Click Next. The Managed Servers window displays.

   1. Click Add to add a managed server.

   2. Enter the Server Name, Listen Address, and the Listen Port for the managed server.

      
      

9. Click Next. The Clusters window displays. Click Add to add a cluster. This is an optional step in the procedure.

   
   

10. Click Next. The Coherence Clusters window displays. Add a coherence cluster. This is an optional step in the procedure.

    
    

11. Click Next. The Machines window displays.

    1. Click Add to add a computer.

    2. Enter the Name and the Node Manager Listen Address.

       
       

12. Click Next. The Assign Servers to Machines window displays. Add both the Admin Server and the managed server to the computer.

    
    

13. Click Next. The Deployments Targeting window displays.

    1. By default, all libraries and applications are only targeted to the Admin Server. Ensure wsm-pm is targeted to AdminServer.

    2. Target all the libraries and applications to the managed server.

       
       

14. Click Next. The Services Targeting window displays.

    1. By default, all services are only targeted to the Admin Server.

    2. Target all services to the managed server.
       

15. Click Next. The Configuration Summary window displays. Verify that all information described in this window is accurate.
    

16. Click Update. The Configuration Progress window displays. The window displays a status message when the domain is updated successfully.
    

17. Click Next. The Configuration Success window displays that describes the Domain Location and Admin Server URL once the configuration is complete.

    
    

18. Click Finish to complete updating the existing domain with the ADF runtime.