4 WebLogic Middleware

This chapter describes the procedure for installing and creating the WebLogic Middleware needed to host OCDS. Important information about the installation and deployment of a BDI Job Admin can be found in the Oracle Retail Bulk Data Integration Installation Guide.

Installing WebLogic

Obtain WebLogic 12c (12.2.1.3.0) by visiting the Oracle Technology Network and taking the following steps.

1. Find fmw_12.2.1.3.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.3.0.0_infrastructure.jar file to run the installer.

3. Run the installer by executing the jar file:

   java -jar fmw_12.2.1.3.0.0_infrastructure.jar

   The Welcome window appears.

4. Click Next. The Auto Updates window appears.

5. Select the appropriate radio button and click Next. The Installation Location window appears.

6. Click Browse to select the Oracle Home location where the WebLogic Server is to be installed.

7. Click Next. The Installation Type window appears.

8. Select Fusion Middleware Infrastructure (JRF and Enterprise Manager) and click Next. The installer performs the pre-requisite checks and ensures all required conditions are satisfied.

9. When the prerequisite check completes successfully, click Next. The Security Updates window appears.

10. Provide information and click Next.

11. Click Install. The Installation Progress window appears.

12. Click Next when the installation completes. The Installation Complete window appears.

Creating Schemas with the Repository Creation Utility (RCU)

The installation of OCDS Job Admin and Injector components requires the existence of schemas in a database prior to installation. These schemas are created and loaded in your database using the Repository Creation Utility (RCU).

This section describes the instructions for running the RCU. See the Oracle Fusion Middleware documentation for detailed instructions on using the RCU.

The following steps will create Oracle AS Repository Components for:

• Common Infrastructure Services

• Oracle Platform Security Services (includes Audit Services)

• WebLogic Services

1. Launch the rcu from ORACE_HOME/oracle_common/bin.

2. Click Next.

   Figure 4-1 Welcome Screen

   
   

3. Select System Load and Product Load, then click Next.

   Figure 4-2 Create Repository Screen

   
   

4. Enter database credentials.

   Figure 4-3 Database Connection Details Screen

   
   

5. Click OK after prerequisites check completes.

   Figure 4-4 Database Connection Details - Checking Prerequisites

   
   

6. The database object created by the RCU will be used during the installation of OCDS (BDI) Job Admin and the OCDS Injector. Choose an appropriate prefix. In addition to the defaults, check the box for Oracle Platform Security Services.

   
   

   Important: Keep track of the Prefix, Schema Owner names, and Passwords used in RCU, they will be needed to deploy OCDS components.

   
   

   Figure 4-5 Select Components Screen

   
   

7. Click Next after Checking Component Prerequisites completes.

   Figure 4-6 Components - Checking Prerequisites

   
   

8. Click OK, enter password, and then click Next.

   Figure 4-7 Schema Passwords Screen

   
   

9. Click Next to accept Default Tablespaces, or click Manage Tablespaces for advanced handling, then click Next.

   Figure 4-8 Map Tablespaces Screen

   
   

10. Click OK to confirm.

    Figure 4-9 Confirm Tablespaces Prompt

    
    

11. Click OK to continue.

    Figure 4-10 Creating Tablespaces Progress Bar

    
    

12. Click Create.

    Figure 4-11 Repository Creation Utility Summary Screen

    
    

13. Click Close when Repository Creation has completed.

    Figure 4-12 Completion Summary Screen

    
    

Creating a WebLogic Domain with JRF

This section describes instructions for creating a new WebLogic domain with JRF, and instructions to create a managed server into which the OCDS Job Admin, Injector, and ORDS components can be deployed.

Prerequisites

The installation of OCDS components requires the existence of schemas in a database prior to installation. These schemas are created and loaded in your database using the Repository Creation Utility (RCU). OCDS requires Oracle WebLogic server 12c (12.2.1.3.0), built with Java 8 (JDK 1.8 64 bit with the latest security updates).

The minimum recommended Java VM memory setting for the OCDS application domain is:

-Xms1024m -Xmx2048m

If re-creating a domain using the same RCU schemas, and those schemas are not in ocds_* tablespaces, then run RCU to drop old RCU schemas.

WebLogic Domain Creation

Perform the following procedure to create a WebLogic Domain with one Managed Server. OCDS can be installed on more than one managed server if preferred.

1. Launch the Fusion Middleware Configuration Wizard from ORACLE_HOME/oracle_common/common/bin.

2. Select Create a new Domain, and enter the domain location.

   Figure 4-13 WebLogic Create Domain Screen

   
   

3. Select Oracle Enterprise Manager to cause the Oracle JRF and WLS Coherence Cluster Extension templates to be selected, in addition to the Basic WebLogic Server Domain template.

   Figure 4-14 Templates Screen

   
   

4. Select the application location.

   Figure 4-15 Application Location Screen

   
   

5. Create a WLS Administrator account.

   Figure 4-16 Administrator Account Screen

   
   

6. Choose a domain mode.

   Figure 4-17 Domain Mode and JDK Screen

   
   

7. Specify the RCU AutoConfiguration. The Schema Owner was created during the RCU step. Complete the form and click the Get RCU Configuration button.

   Figure 4-18 Database Configuration Type Screen

   
   

8. Click Next, if the Connection Result Log is error free.

   Figure 4-19 Database Configuration Type Screen - Displaying Result Log

   
   

9. Accept defaults, then click Next (unless you need to edit schema passwords because they are not all the same).

   Figure 4-20 Component Datasources Screen

   
   

10. Test the selected connections. If all connections are successful, click Next.

    Figure 4-21 JDBC Test Screen

    
    

11. Select the settings according to the deployment topology and click Next. The Managed Server is shown here.

    Figure 4-22 Advanced Configuration Screen

    
    

12. Choose the server name and ports, and enable SSL. Then click Next.

    Figure 4-23 Administration Server Screen

    
    

13. Select the Node Manager Type, and enter the Node Manager Credentials, then click Next.

    Figure 4-24 Node Manager Screen

    
    

14. Click the Add button.

    Figure 4-25 Managed Servers Screen

    
    

15. Enter the Managed Server name and ports, then click Next.

    Figure 4-26 Managed Servers Screen - Displaying Server Name

    
    

16. Click Next if skipping the cluster configuration, or click Add to enter information. Then click Next.

    Figure 4-27 Clusters Screen

    
    

17. Click Next if skipping the Server Templates, or click Add to enter the information. Then click Next.

    Figure 4-28 Server Templates Screen

    
    

18. Click Next if no changes are required.

    Figure 4-29 Coherence Clusters Screen

    
    

19. Click Add to enter the machine information.

    Figure 4-30 Machines Screen

    
    

20. Enter the machine and click Next.

    Figure 4-31 Machines Screen - Displaying Machine Name

    
    

21. Assign the managed server to the machine by selecting the managed server on the left, and the machine on right, then click the right arrow.

    Figure 4-32 Assign Servers to Machines Screen

    
    

22. Click Next.

    Figure 4-33 Assign Servers to Machines Screen - Servers Assigned

    
    

23. Click Next to skip virtual targets.

    Figure 4-34 Virtual Targets Screen

    
    

24. Click Next to skip partitions.

    Figure 4-35 Partitions Screen

    
    

25. Review the domain configuration, then click Create.

    Figure 4-36 Configuration Summary Screen

    
    

26. Click Next. The Configuration Progress is displayed.

    Figure 4-37 Configuration Progress Screen

    
    

27. Click Finish at the confirmation page.

    Figure 4-38 End Of Configuration Screen

    
    
    
    

    Note: At this point the new node manager will have SecureListener enabled by default.

    
    

    • QA systems may prefer to disable this feature. If so, edit <DOMAIN_HOME>/nodemanager/nodemanager.properties and set SecureListener=false.

      Figure 4-39 Example - SecureListener Property

      
      

    • In this case, after starting the Node Manager and WebLogic, set the Node Manager's Type to Plain on the machine, by navigating to Home - Machines - [machine] - Node Manager. Then click Save.

      Figure 4-40 Node Manager Screen with Type Setting Plain

      
      

    • Finally, bounce node manager, and then WebLogic.

28. Start the Node Manager ($DOMAIN_HOME/bin/startNodeManager.sh).

29. Start the Domain ($DOMAIN_HOME/bin/startWebLogic .cmd).

    
    

    Note: Once the console is up you can start the managed server and configure SSL (if needed)

    
    

30. Start the Managed Server. If you are using the Admin Console, navigate to Home - {Domain} - Summary of Servers - Control (tab), then select managed server and click Start.

31. Configure SSL on Managed Server.

    Figure 4-41 OCDS Managed Server

    
    
    
    

32. Add the following security policy to $ORACLE_HOME/wlserver/server/lib/weblogic.policy file.

    grant codeBase "file://-" { permission java.security.AllPermission; permission oracle.security.jps.service.credstore.CredentialAccessPermission "credstoressp.credstore", "read,write,update,delete"; permission oracle.security.jps.service.credstore.CredentialAccessPermission "credstoressp.credstore.*", "read,write,update,delete"; };

33. Set JTA timeout to 43200.

    1. Log in to Admin console.

    2. Click on the domain name.

    3. Select the JTA tab and change the timeout value to 43200.

       
       

       Note: The last two steps are part of the requirements for jobadmin deployment, see the Oracle Retail Bulk Data Integration Installation Guide for additional information.