Section - 2 : Single Node Installation


If you selected ‘1’ in the following screen:

Enter the details as shown in the following sections:

Linux User/Group Section

  1. Linux Username

    • Example: oracle (the user you installed Fusion Middleware with)

  2. FMW Products Installed Group

    • Example: oinstall or oracle (the user group you installed Fusion Middleware with)

Database Section

OIDG and RCU Schemas are Created in the Same Database Instance:

IS OIDG Schema and RCU Infra Schemas were created on the Same Database/Pluggable Database (y/n): y

Enter the following values to proceed further:

Database hostname: Database hostname
Database service name: DB Instance name
Database port: Listener port (Example: 1521)
Database OIDG User name: ‘OIDXAPPUSER’
RCU Infra Schema Prefix: RCU Schema’s Prefix

OIDG and RCU Schemas Are Created in Different Database Instances:

IS OIDG Schema and RCU Infra Schemas were created on the Same Database/Pluggable Database (y/n): n

Enter the DB Inputs:

RCU Database hostname: Database hostname
RCU Database service name: DB Instance name
RCU Database port: Listener port (Example: 1521)
RCU Infra Schema Prefix: RCU Schema’s Prefix
OIDG Database User name: ‘OIDXAPPUSER’
OIDG Database hostname: OIDG Database hostname
OIDG Database service name: OIDG DB Instance name
OIDG Database port: OIDG Listener port (Example: 1521)

Middleware Section

  • OIDG Fusion Middleware HOME Path:
    • Enter the middleware home path including Oracle_Home

OIPA Server Input Section

Provide the OIPA server inputs

Confirmation Section

Correct? (y/n) : (y/n)

Credentials Section

WebLogic Credentials

  • Set the WebLogic User Password
    • You have to use this password for WebLogic login after domain creation.

Note: Password must contain atleast 8 characters long and The number of numeric or special characters in a password cannot be less than 1.

Database Credentials

  • Set the RCU Password for all Schemas

    Provide the common password used for the RCU Infra Schemas

  • Set the password for OIDG's schema:

    Provide the password for the OIDXAPPUSER.

GnuPGCredentials

  • Set the password for PGP keys

    Set the password for PGP Key creation for Encryption/Decryption

    Note: Password must contain atleast 8 characters long and the number of numeric or special characters in a password cannot be less than 1.

Security Realm user Credentials

Note: Users oidguser and oidgpii are created for configuring Security Credentials in EM and Encryption of PII Data

  • OIDG User Password:

    Note: Password must contain atleast 8 characters long and The number of numeric or special characters in a password cannot be less than 1.

  • PII Password:

    Note: Password must contain atleast 8 characters long and The number of numeric or special characters in a password cannot be less than 1.

Confirmation

Please verify and resolve any errors that have occurred before running sh install_oidg.sh. If no errors found please run below command.

Command :

 sh install_oidg.sh

Note: If the Pre/Post Script fails below are the steps to follow

Follow these steps in case of pre-script failures: Drop and Re-create the RCU Schema.

  1. Delete the middleware user_projects folder and domain_registry.xml.
  2. Example: /FMW_HOME/Oracle/Middleware/Oracle_Home/user_projects

  3. Delete the OIDG folder.
  4. Example: /FMW_HOME/Oracle/Middleware/oidg

  5. Delete ora_stage folder.
  6. Example: /FMW_HOME/oraStage

  7. Stop all the running WebLogic processes if there are any.
  8. Re-run from the input parameters for OIDG Installation chapter with new RCU Schemas.

OIDG Installation Manual Steps

Defining JNDI Providers

JNDI Provider resources are required by OSB components to locate and communicate with Enterprise Java Beans (EJB) components.

  1. Log on to the Service Bus console (http://hostname:port/sbconsole), where “hostname:port” are the host name and port of your administration server.
  2. In the project explorer, navigate to All Projects → System → JNDI Providers.
    Verify that DataServices_JNDIProvider is defined.
    If it is defined, skip steps 3-7. If not, continue with the rest of the steps.
  3. In the upper left corner of the page, click Create to begin a new update session.
  4. Right-click the JNDI Providers folder to display the context menu, then click Create → Create JNDI Provider.
    Image represents creating JNDI provider.
    Figure 3.2.1 - Create JNDI Provider
  5. In the Create JNDI dialog, enter “DataServices_JNDIProvider” for Resource Name. Click Create.
    Figure 3.2.2 - Create JNDI Dialog
  6. On the JNDI Definition page, fill in the following fields:
    1. Provider URL – the host name or IP and port of the managed server to which OIDX_POC_DSL is targeted (Example: “t3://hostname:port”) i.e. ‘AML Server’.
    2. Initial Context Factory – select “weblogic.jndi.WLInitialContextFactory”
    3. User Name, New Password, and Confirm Password – the login credentials for the server. Usually credentials are the same as administration server login credentials.
      Image represents JNDI definition
      Figure 3.2.3 - JNDI Definition
  7. Click Save located on the upper-right corner of the page.
    Image represents Save icon
    Figure 3.2.4 - Save Icon
  8. Click Activate once changes are saved and verify if the changes are activated or not by refreshing the page.

Creating Security Policies

  1. Log in to the WebLogic Enterprise Manager (<hostname>:< Admin Server Port Number>/em) with WebLogic credentials.
  2. WebLogic Domain → Security → System Policies.
    Image represents web logic enterprise options
    Figure 3.2.5 - WebLogic Enterprise
  3. Under Search section, select Name as Includes.
    Image represents search section
    Figure 3.2.6 - Search Section
  4. Type “OIDX_POC_DSL” in the search box, and click the arrow icon.
    Image represents search box
    Figure 3.2.7 - Search Box
  5. Check to see if the search results include a row as shown below.
    Image represents search result area
    Figure 3.2.8 - Search Result Area
  6. If this policy does not exist, create it by following these steps:
    1. Select the row that includes the text oracle.wsm.console.core.view, and then click Create Like.
    2. Image represents create like
      Figure 3.2.9 - Create Like

    3. On the Create System Grant Like page, change the text in the Codebase box to the following: file:${oracle.deployed.app.dir}/OIDX_POC_DSL${oracle.deployed.app.ext}
    4. Select the CredentialAccessPermission row in the Permission Class table and click Edit.
    5. In the Edit Permission dialog change Permission Actions from read,write,delete,update to just read. Click Ok.
    6. Click Ok again.

OIDG Post Script Installation

After completing the steps in 'OIDG Installation Manual Steps' topic run the following command from root to complete the installation.

Command:

 sh install_oidg_post.sh   (from root)

Please check the status of Chef Script: Finished (or) Failed

Note: Script run usually takes about 20-30 minutes to complete all the deployments.

Note: After Post Script Installation follow Extension Deployment steps. Please refer to “OIDG Extension Deployment” and “OIDG Extension installation using Chef scripts” sections.

Deploying ACORD_AML Libraries

In August 2017, ACORD stopped making the AML specification available to non-members. As a consequence of this and the associated licensing changes, OIDX cannot include the AML XSD as part of its deployments. The user must independently acquire a copy of the AML XSD distribution (ACORD Asia Pacific GI XML - 1.2.0 - Members.zip) and install the schema resources into the OIDX service virtualization deployment.

XSD Installation

Follow these steps:

  1. Log into the Service Bus Console (<hostname>:<Admin Server port number>/sbconsole).
  2. Create a new update session by clicking Create..
    Image represents importing ZIP file.
    Figure 3.2.10 - Oracle Service Bus Console
  3. Click Import.
    Image represents secelting zip file from your local drive.
    Figure 3.2.11 - Import from Local Drive
  4. Click Choose File and upload the file.
    Image represents imported heirarchy.
    Figure 3.2.12 - Choosing and uploading file
  5. Click Next (right arrow).
    Image represents select all except highlighted files.
    Figure 3.2.13 - Next button
  6. Click Import.
    Image represents the root aml folder structure.
    Figure 3.2.14 - Import button
  7. Click Close.

    Image represents the root aml folder structure.
    Figure 3.2.15 - Close button
  8. Click Activate once the steps finished.

OIDG Release Upgrade Prerequisite

Delete old files from the following locations and replace them with the new release files:

  1. Copy the following files from the OIDG release package to /<user home base>/Chef/OIDG
    • AdminView.ear
    • log4j-api-2.9.1.jar
    • log4j-core-2.9.1.jar
    • OIDX_POC_DSL.ear
    • OIDX_PrcOrch_cfgplan.xml
    • OSBCoreCustomizationFile.xml
    • QuickView.ear
    • IDXPORTAL.ear
    • sca_ResultProcessing.jar
    • ResultProcessing_cfgplan.xml
    • sca_OIDX_PrcOrch.jar
    • SVCore_SrvVirt.sbar
  2. Copy the files below from the OIDG release package to /user home base/Chef/OIDG/config
    • adapter-oidx-cache-config.xml
    • configfilesecurity.key
    • oidx_dsl_log4j.xml
    • PIIConfig.xml
    • oidx_cache_config.xml

OIDG Release Deployment / Un-Deployment Process

  1. Navigate to the path /OIDG_Automation/SingleNode_12.2.1.3/OIDG-CoreInstallation/chef and run: sh dep_undep_app_config.sh from root.
  2. Select 1 for OIDG Deploy/Un-Deploy (or) 2 for Exit
  3. Select the components you want to undeploy and replace from the new release package.
    1) AdminView [ y / n ] : (y/n)
    2) QuickView               [ y / n ] : (y/n)
    3) Data Services          [ y / n ] : (y/n)
    4) SOA Composite          [ y / n ] : (y/n)
    5) Service Virtualization [ y / n ] : (y/n)
    6) IDX Portal             [ y / n ] : (y/n)
    7) SOA Result Processing  [ y / n ] : (y/n)

  4. Provide the Linux user/group and Middleware Home details.
    • Linux Username:
      • Example: oracle (the user you installed Fusion Middleware with)
    • Linux Groupname:
      • Example: oinstall or dba (the group you installed Fusion Middleware with)
    • FMW Middleware Home:
      • Middleware home path including Oracle_Home
        Example: /Path/Oracle/Middleware/Oracle_Home
    • All the inputs given are Correct? (y/n) : (y/n)
    • WebLogic User Password
  5. Check the Confirmation.

OIDG Release Undeployment Process

  1. Navigate to /OIDG_Automation/SingleNode_12.2.1.3/OIDG-CoreInstallation/chef and run sh install_undep_app.sh from root
  2. Check the status of Chef Script: Finished or Failed

Please verify the status of Undeployment components from WebLogic console and EM.

OIDG Release Deployment Process

  1. Navigate to /OIDG_Automation/SingleNode_12.2.1.3/OIDG-CoreInstallation/chef and run: sh install_dep_app.sh from root.
  2. Check the status of Chef Script: Finished or Failed.

Please verify the status of deployed components from the WebLogic and EM consoles.

WebLogic Performance Tuning Settings

This chapter describes deployment settings that may need to be adjusted depending on environmental factors. This application integrates with external services that may have requirements where these settings should be adjusted for optimal performance. In addition, hardware, co-location, and networking may require adjustments to these settings.

These are the recommended default settings:

  1. Update the ‘Stuck Thread Timer Interval’ value to 36000 AML server.
    Home Page → Environment Servers → aml_server → Configuration → Tuning → Update ‘Stuck Thread Max Time’ and click on save.
    Image represents thread max time.
  2. Update the ‘Stuck Thread Timer Interval’ value to 1800 for OSB and SOA servers:
    Home Page → Environment Servers → OSB_server → Configuration → Tuning → Update ‘Stuck Thread Max Time’ and click on save
    Image represents Stuck thread max time
    Note: Repeat the above steps for SOA Server
  3. Update the SOA Data source connection pool size to 200.
    Home Page → Services → Data Sources
    Image represents Go to Data Sources.
    Figure 3.2.16 - Go to Data Sources
  4. Click the SOA Datasource under 'Summary of JDBC Data Sources' section.
  5. Go to the SOA Datasource → Connection → Pool Maximum Capacity.
  6. Enter 200 and click Save.
  7. Click Transactions tab and select Set XA Transaction Timeout check box. Make sure XA Transaction Timeout value is set to 0.
    Image represents Settings for SOADataSources.
    Figure 3.2.17 - Settings for SOADataSources
  8. Click Save.

Note: Click the 'View changes and restarts' link in Change Center section (located at the top left corner of the page) of WebLogic admin console and click 'Restart Checklist' tab. Select and click Restart if any resource types are listed in the 'Server Restart Checklist' table.

Configure Memory Arguments

Set min and max memory arguments to 4GB for aml_server, soa_server and osb_server managed servers.

  1. Click Home Page → Environment Servers → Aml_server → Configuration → Server Start → Update ‘Arguments’
    Image represents Configuring Memory Arguments.
    Figure 3.2.18 - Configuring Memory Arguments
  2. Click Save.

Note: Repeat the above step for osb_server1 and soa_server1.

Update DI properties

  1. Click Home PageEnvironmentServersSoa_serverConfiguration → 8. Click on Activate once the steps finished.→ Update ‘Arguments’ to ‘-Dcom.ibm.CORBA.UseSchemaIDR=false’
    Image represents updating DI properties.
    Figure 3.2.19 - Updating DI Properties
  2. Click Save and click Active Chnages.