Create and Configure OIPA

Create and Configure the OIPA Application Server

  1. Select Servers>New server.
  2. Select server type WebSphere application server.
  3. Enter OIPA for the name of the server.
  4. Click Next.
  5. Select the default server template.
  6. Click Next.
  7. Ensure Generate Unique Http Ports is checked.
  8. Confirm the new server by clicking Finish.
  9. After the application has been created, review the messages at the top of the Application servers screen to confirm that the new server has been created successfully.
  10. Navigate to the OIPA server by clicking on its name within the list of application servers.
  11. Click the Session management link in the Container Settings section.
  12. Verify that Enable Cookies is checked. This is checked by default.
  13. Click the Enable Cookies link and verify that 'Restrict cookies to HTTPS sessions' is unchecked. (This is unchecked by default.)
  14. Click OK.
  15. Click OK to save the configuration changes.

Note: These instructions assume that a fresh installation of the application server was performed. All configuration settings must use the default settings unless otherwise noted. If the application server has been used for previous deployments, you may want to create a new application server specifically for the deployment of the OIPA environment.

Configure WebSphere Environment Variable for Database Driver

  1. 1.A variable must be used to define the location where the database driver is located. The name of the variable depends on the type of database.
    • Oracle: ORACLE_JDBC_DRIVER_PATH
    • IBM DB2: DB2UNIVERSAL_JDBC_DRIVER_PATH and DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH
    • SQL : MICROSOFT_JDBC_DRIVER_PATH
  2. Select Environment>WebSphere Variables.
  3. Select the scope of the OIPA server from the drop-down list.
  4. Click New.
  5. Enter the name of the database driver variable, as listed above.
  6. In the Value field, enter the path to the directory where the database driver is located. For example:/opt/oracle/db_drivers or C:\oracle\oipa\db_drivers
  7. Click OK.

Configure the OIPA Application Server

JVM Settings

  1. Navigate to Servers>Server Types>WebSphere application servers.
  2. Select the OIPA application server.
  3. Expand Java and Process Management.
  4. Select Process Definition.
  5. Select Java Virtual Machine.
  6. In the Classpath text box, enter the location of the OIPA property files.

    Example: /opt/oracle/oipa/conf/ or c:\oracle\oipa\conf\

    Note: Be sure to include the trailing slash (/ or ) character.

  7. Set Initial Heap Size to 512.
  8. Set Maximum Heap Size to 2048.
  9. In the Generic JVM Arguments text box, enter the following arguments, replacing the location of each file (highlighted) with the correct location for the configuration.

    Note: You may find it easier to copy the text below to a text editor and make the necessary changes there, then copy and paste it into the JVM Arguments text box.

-Duser.language=en -Duser.region=US -Djava.net.preferIPv4Stack=true -Djava.net.preferPv6Addresses=false -javaagent:/opt/oracle/oipa/libs/spring-instrument-4.3.10.RELEASE.jar -Dtangosol.coherence.override=/opt/oracle/oipa/conf/coherence-config.xml -Dtangosol.coherence.cacheconfig=/opt/oracle/oipa/conf/coherence-cache-config.xml -Dtangosol.pof.config=com-adminserver-pas-web-pof-config.xml -Dtangosol.coherence.mode=prod -Djava.util.logging.config.file="/opt/oracle/oipa/conf/logging.properties"

  1. Click OK.
  2. Follow the below steps to disable IBM JAXRS Engine.
    1. Navigate to Servers -> Server Types -> WebSphere application servers
    2. Select the OIPA application server
    3. In the Server Infrastructure area, select Java and Process Management -> Process definition.
    4. In the Server Infrastructure area, select Process Definition.
    5. In the Additional Properties area, select Java VirtualMachine.
    6. In the Additional Properties area, select Custom Properties.
    7. Select the New box.
    8. In the Name entry field, type:

      com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine

      com.ibm.websphere.webservices.UseWSFEP61ScanPolicy

    9. In the Value entry field, type true

    10. Select OK.

  1. Follow the below steps to disable WebSphere Application Server JPA initialization, because JPA initialization is done from OIPA.
    1. Navigate to Servers -> Server Types -> WebSphere application servers
    2. Select the OIPA application server
    3. In the Server Infrastructure area, select Java and Process Management -> Process definition.
    4. In the Server Infrastructure area, select Process Definition.
    5. In the Additional Properties area, select Java Virtual Machine.
    6. In the Additional Properties area, select Custom Properties.
    7. Select the New box.
    8. In the Name entry field, type:
    9. com.ibm.websphere.persistence.ApplicationsExcludedFromJpaProcessing

    10. In the Value entry field, type the names of the applications to be excluded from JPA processing. If there are multiple applications, separate each with the ":" character. If you wish to specify all applications simply type the "*" character.
    11. Select OK.

Configure the Listening Port

  1. Select Servers>Server Types>WebSphere application servers.
  2. Select the OIPA server.
  3. In the Communications section, select Ports.
  4. Note the port listed for WC_defaulthost.
  5. If the port number needs to be changed, select the WC_defaulthost port.
  6. Modify the Port text box as needed.
  7. Click OK.

Configure the Virtual Host

  1. Select Environment > Virtual Hosts.
  2. Click default_host.
  3. Click Host Aliases.
  4. Click New.
  5. Enter the port assigned for WC_defaulthost in the previous listening port section.
  6. Click OK.

Create Data Sources

Add the JDBC Provider

  1. Select Resources>JDBC>JDBC providers.
  2. Select the scope of the server from the drop-down list (the drop-down list displays if the "Show scope selection drop-down list…" is checked).
  3. Click New.
  4. Select the Database type.
    • For Oracle, select Oracle.
    • For DB2, select DB2.
    • For SQL, select SQL Server.
  5. Select the Provider type.
    • For Oracle, select Oracle JDBC Driver.
    • For DB2, select DB2 Universal JDBC Driver Provider.
    • For SQL, select Microsoft SQL Server JDBC Driver.
  6. Select Implementation type.
    • For Oracle, select XA data source.
    • For DB2, select XA data source.
    • For SQL, select XA data source.
  7. Click Next.
  8. Enter the variable name used for the database driver.
    • For Oracle, enter ${ORACLE_JDBC_DRIVER_PATH}
    • For DB2, click Next.
    • For SQL, click Next.

  9. Click Finish

    Note: For Oracle, skip steps 10 and 11. For DB2, continue at step 10.

  10. Click on the newly created JDBC provider.
  11. Confirm that the class path field is set to correctly reference the two DB2 and SQL drivers. Refer to the examples below. Edit the field if needed.
  12. For DB2

    For SQL

  13. Click OK.

Create the Data Sources

The following four data sources must be created:

A readonly database user should be used for ADMINSERVERRESOURCEDS, ADMINSERVERSEARCHDS and ADMINSERVERREADONLYDS.Repeat the following steps for each data source, replacing <DATASOURCE_NAME> with the specific data source being configured.

  1. Select Resources>JDBC>Data sources.
  2. Click New.
  3. For the data source name, enter <DATASOURCE_NAME>.
  4. For the JNDI name, enter <DATASOURCE_NAME>.
  5. Click Next.
  6. Select the JDBC provider created in the last step.
  7. Click Next.
  8. Enter the database connection information.
    • For Oracle, enter the database information in the following format:

      jdbc:oracle:thin:@hostname:port:SID

    • For DB2, enter the database name, hostname and port.
  9. Uncheck the checkbox for Use this data source in container managed persistence.
  10. Click Next.
  11. On the Setup security aliases screen, click Next.
  12. Click Finish.
  13. Select <DATASOURCE_NAME> from the list of data sources that appears.
  14. Select Custom Properties.
  15. Click New to create new variables for each property listed below.
    • For Oracle:

      Name: user; Value: database user name

      Name: password; Value: database password

    • For DB2:

      Name: user; Value: database user name

      Name: password; Value: database password

      Name: currentSchema; Value: schema name (only needed for readonly data source)

    • For SQL:

      Name: user; Value: database user name

      Name: password; Value: database password

  16. In the Messages area at the top of the screen, click the link for Save to the master configuration.
  17. Once complete, return to the Datasources screen and use the Test Connection button on the main data source list to confirm that the settings were successful for each data source.

 

 

 

 

 

Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us