Skip Headers

Oracle® Health Sciences Information Gateway CONNECT Gateway and Adapter Installation and Configuration Guide Release 2.0.1 E37024-02 |
Home | Book List | Contents | Index | Contact Us

Previous | Next
| PDF · Mobi · ePub

# B Configuring Oracle CONNECT Adapters with Oracle Components

This appendix contains the following topics:

- Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Registry

- Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Healthcare Master Person Index

- Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Repository

## B.1 Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Registry

1. Log into the OHIG adapter.

2. Edit the file `<config_nhin_dir>/internalConnectionInfo.xml`.

   GlassFish example:

       <glassfish_install_dir>/domains/<domain_name>/config/nhin/internalConnectionInfo.xml

   WebLogic example:

       <weblogic_install_dir>/user_projects/domains/<domain_name>/config/nhin/internalConnectionInfo.xml

3. Edit or create the business service `adapterxdsbdocregistrysoap12`. Ensure `<accessPoint>` is defined as:

       <accessPoint useType="endPoint">http://<oracle_registry_host_ip>:8080/hrl/regsvc</accessPoint>   <categoryBag>     <keyedReference tModelKey="uddi:nhin:versionofservice" keyName="" keyValue="1.0"/>     <keyedReference tModelKey="CONNECT:adapter:apilevel" keyName="" keyValue="LEVEL_a0"/>         </categoryBag>

   Note:

   If you have selected non-default home community ID (other than 1.1) for the HIG installation, ensure that you provide an appropriate value for the businessKey attribute of the businessService element.

   For example, if you have selected home community ID as 4.4, the businessKey value should be set to `uddi:testnhieonenode:4.4`.

4. Edit or create the business service `adapterxdsbdocregistry`. Change to the `<accessPoint>` from:

       <accessPoint useType="endPoint">http://<adapter_host_ip>:8080/CONNECTAdapter/DocumentRegistry_Service</accessPoint>

   to

       <accessPoint useType="endPoint">http://<adapter_host_ip>:8080/CONNECTAdapterDocRegSoap12/AdapterDocRegistry2Soap12Service</accessPoint>  <categoryBag>    <keyedReference tModelKey="uddi:nhin:versionofservice" keyName="" keyValue="1.0"/>    <keyedReference tModelKey="CONNECT:adapter:apilevel" keyName="" keyValue="LEVEL_a0"/>  </categoryBag>

5. Edit the file `<config_nhin_dir>/repository.properties` and edit or create the following property:

       convertPnR2SOR=true

   Note:

   The property `convertPnRSOR` should only be set to `true` when using the internal test repository with Oracle Registry.

6. Restart the application server.

## B.2 Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Healthcare Master Person Index

1. Log into the OHIG adapter host.

2. Edit the file `<config_nhin_dir>/internalConnectionInfo.xml`.

   GlassFish example:

       <glassfish_install_dir>/domains/<domain_name>/config/nhin/internalConnectionInfo.xml

   WebLogic example:

       <weblogic_install_dir>/user_projects/domains/<domain_name>/config/nhin/internalConnectionInfo.xml

3. Edit or create the business service `adaptercomponentmpiservice`. Change the `<accessPoint>` from:

       <accessPoint useType="endPoint">http://<adapter_host_ip>:8080/Adapter/PatientDiscovery/A_0/AdapterComponentMpiService</accessPoint>

   to

       <accessPoint useType="endPoint">http://<adapter_host_ip>:8080/AdapterComponentIheMpi/AdapterComponentMpiService</accessPoint>

4. Edit or create the business service `adaptercomponentmpisecuredservice`. Change the `<accessPoint>` from:

       <accessPoint useType="endPoint">https://<adapter_host_ip>:8181/Adapter/PatientDiscovery/A_0/AdapterComponentMpiSecuredService</accessPoint>

   to

       <accessPoint useType="endPoint">https://<adapter_host_ip>:8181/AdapterComponentIheMpi/AdapterComponentMpiSecuredService</accessPoint>

5. Edit the file `<config_nhin_dir>/AdapterComponentIheMpiConfig.properties` and edit or create the following property:

       ihempi.pdq.v3.endpoint.url=http://<oracle_mpi_host_ip>:8080/PDQSupplier_Service/PDQSupplier

6. Restart the application server.

## B.3 Configuring Oracle Health Sciences Information Gateway CONNECT Adapter with Oracle Repository

1. Log into the OHIG adapter.

2. Edit the file `<config_nhin_dir>/internalConnectionInfo.xml`.

   GlassFish example:

       <glassfish_install_dir>/domains/<domain_name>/config/nhin/internalConnectionInfo.xml

   WebLogic example:

       <weblogic_install_dir>/user_projects/domains/<domain_name>/config/nhin/internalConnectionInfo.xml

3. Edit or create the business service `adapterxdsbdocrepositorysoap12retrieve`. Ensure `<accessPoint>` is defined as:

       <accessPoint useType="endPoint">https://<oracle_repository_host_ip>:7778/XDS/xdsrepositoryb_Soap12</accessPoint>
          <categoryBag>       <keyedReference tModelKey="uddi:nhin:versionofservice" keyName="" keyValue="1.0"/>       <keyedReference tModelKey="CONNECT:adapter:apilevel" keyName="" keyValue="LEVEL_a0"/>    </categoryBag>

   Note:

   If you have selected non-default home community ID (other than 1.1) for the HIG installation, ensure that you provide an appropriate value for the businessKey attribute of the businessService element.

   For example, if you have selected home community ID as 4.4, the businessKey value should be set to `uddi:testnhieonenode:4.4`.

4. Edit or create the business service adapterxdsbdocrepositorysoap12pnr. Ensure `<accessPoint>` is defined as:

       <accessPoint useType="endPoint">https://<oracle_repository_host_ip>:7778/XDS/xdsrepositoryb/iti41</accessPoint>
          <categoryBag>       <keyedReference tModelKey="uddi:nhin:versionofservice" keyName="" keyValue="1.0"/>       <keyedReference tModelKey="CONNECT:adapter:apilevel" keyName="" keyValue="LEVEL_a0"/>    </categoryBag>

   Note:

   If you have selected non-default home community ID (other than 1.1) for the HIG installation, ensure that you provide an appropriate value for the businessKey attribute of the businessService element.

   For example, if you have selected home community ID as 4.4, the businessKey value should be set to `uddi:testnhieonenode:4.4`.

5. Edit or create the business service `adapterxdsbdocrepository`. Change the `<accessPoint>` from:

       <accessPoint useType="endPoint">http://<adapter_host_ip>:8080/CONNECTAdapter/DocumentRepository_Service</accessPoint>

   to

       <accessPoint useType="endPoint">http://<adapter_host_ip>:8080/CONNECTAdapterDocReposSoap12/AdapterDocRepository2Soap12Service</accessPoint>   <categoryBag>     <keyedReference tModelKey="uddi:nhin:versionofservice" keyName="" keyValue="1.0"/>     <keyedReference tModelKey="CONNECT:adapter:apilevel" keyName="" keyValue="LEVEL_a0"/>   </categoryBag>

6. Ensure to comment-out the business service adapterxdsbdocrepositorysoap12 element.

7. Restart the application server.

Note:

To avoid the exception, javax.net.ssl.SSLException: Received fatal alert: illegal_parameter, execute the following steps.

GlassFish

Add the following JVM options from Glassfish admin console and restart the server:

- `-Dcom.sun.net.ssl.enableECC=false`

- `-Djsse.enableSNIExtension=false`

WebLogic

Add the following JVM options to the OHIG Connect WebLogic script:

- `-Dcom.sun.net.ssl.enableECC=false`

- `-Djsse.enableSNIExtension=false`

To set these JVM options, perform the following steps:

1. Navigate to the scripts directory using the following command:

   `$ cd <install_dir>/addons/connect/scripts`

2. Open the script file using the following command:

   `$ vi connect-start-weblogic.sh`

3. Add the following commands before the `export JAVA_OPTIONS` command:

   `JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.net.ssl.enableECC=false"`

   `JAVA_OPTIONS="$JAVA_OPTIONS -Djsse.enableSNIExtension=false"`

4. Save the changes and restart the server.