| Oracle® Health Sciences Adverse Event Integration Pack for Oracle Health Sciences InForm and Oracle Argus Safety Installation Guide for On-Premise Deployment Release 1.0.2 E49877-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Health Sciences Adverse Event Integration Pack for Oracle Health Sciences InForm and Oracle Argus Safety Installation Guide for On-Premise Deployment Release 1.0.2 E49877-01 |
|
|
PDF · Mobi · ePub |
This chapter contains the following topics:
Section 7.1, "Installing the Adverse Event: InForm and Argus Safety Integration"
Section 7.2, "Configuring Pre-deployment Security for the InForm-Argus Safety Integration"
Section 7.3, "Configuring the Adverse Event: InForm and Argus Safety Integration"
Section 7.5, "Deploying the Adverse Event: InForm and Argus Safety Integration"
To install the Adverse Event: InForm and Argus Safety integration, perform the following steps:
Download Oracle® Health Sciences InForm and Oracle Argus Safety Integration Release 1.0 from the edelivery page.
Unzip aia-inform_argus-pip.zip to any location on the server.
Navigate to inform_argus-pip > Disk1.
Execute the following commands, based on your platform.
Table 7-1 Launching the Adverse Event: InForm and Argus Safety Installer
| Field | Description |
|---|---|
|
Linux x86 (64-bit) Solaris SPARC (64-bit) |
At the command line prompt, enter: ./runInstaller -invPtrLoc <soa_Home>/oraInst.loc -jreloc <location of the jre specific to your operating system. This directory should have /bin/java> |
|
Microsoft Windows (32-bit or 64-bit) |
Double-click setup.exe. |
The Welcome screen is displayed, listing prerequisites and information about how to begin the installation process.
Click Next.
Wait for the following prerequisite checks to complete:
Operating system certification
Recommended operating system packages
Kernal parameters
Recommended gilbc version
Physical memory
When the prerequisite checks are complete, click Next.
The Installation location screen is displayed.
Select the AIA Home where the Foundation Pack is installed.
Click Next.
The Installation Summary screen is displayed.
Review the installation summary. To save the Response file, click Save.
The Response file stores the values that you previously entered and are on the summary page.
If you want to install again, you can run a command and the installer performs a silent install with inputs from the Response file instead of using the wizard. The following is an example of the command. Note the -silent and -response arguments.
./runInstaller -invPtrLoc <SOA_Home>/oraInst.loc -jreLoc <location of the jre for your operating system> -silent -response <Oracle Home>/11.1_Installer_response.xml
Note:
he location of the jre for your operating system should have the format /bin/java. Do not use a hard coded value for java dir.Click Install.
A warning message is displayed indicating that any customizations will be overwritten.
Click Yes to proceed with the installation.
Alternatively, if you click No, you can go back to the previous screen. For more information on how to back up AIA_HOME and preserve customizations, see Section 4.4.
Click Next.
The Installation Progress screen is displayed.
Click Next.
The Installation Complete screen is displayed.
Click Finish.
The installation is complete.
The Adverse Event: InForm and Argus Safety integration stores messages containing patient data in a JMS Queue on the SOA server. The JMS Queue must reside in an encrypted tablespace in the SOA database.
To configure pre-deployment security, perform the following steps:
Create or open the sqlnet.ora file from $ORACLE_HOME/network/admin.
For example:
<Oracle Home>/db11g/product/11.2.0/dbhome_1/network/admin.
To create a wallet that is used by the TDE encryption, follow the instructions in Oracle® Database Advanced Security Administrator's Guide 11g Release 2 (11.2).
Ensure that the following line is present in the sqlnet.ora file. If it is not present, add it at the end of the file.
ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=<ORACLE_BASE >/admin/<ORACLE_SID >/wallet/)))
For example:
ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=<Oracle Home>/db11g/admin/phrmdev2/wallet/)))
Save the sqlnet.ora file.
Navigate to <AIA_HOME>/data/AEInFormandArgus/sql/JMSEncryption.
Open CreateSecureTableSpace.sql in an editor.
Locate the string <ORACLE_HOME>/db11g/admin/<ORACLE_SID>/secure01.dbf in CreateSecureTableSpace.sql and replace it with the appropriate location on your database server. Change any parameters for the tablespace to suit your environment.
For example:
/slot/machinename/xxxx.dbf
Save CreateSecureTableSpace.sql.
Using SQL*Plus, connect to the database as a user with the SYSDBA role.
For example:
sqlplus <username> as sysdba
Press Enter.
Enter <password>.
Execute CreateSecureTableSpace.sql.
For example:
SQL> @ /<AIA_HOME>/data/AEInFormandArgus/sql/JMSEncryption/CreateSecureTableSpace.sql
The SQL script prompts for the wallet password. Enter the wallet password provided during wallet creation. When the script executes successfully, a secure tablespace is created.
Exit SQL*Plus.
Using SQL*Plus, connect to the database as a user with the <AIA_INSTANCE>_JMSUSER role.
For example:
sqlplus <username>@<db sid>
Press Enter.
Enter <password>.
Note:
The script CreateSecureTable.sql can only be run once. If you run it second time, it deletes the existing table before creating a new one.Execute CreateSecureTable.sql.
For example:
SQL> @ <AIA_HOME>/data/AEInFormandArgus/sql/JMSEncryption/CreateSecureTable.sql
When the script executes successfully, a secure tablespace is created in the <AIA_INSTANCE>_JMSUSER schema.
Exit SQL*Plus.
The configuration wizard screens prompt you to enter the data that is required for successful configuration of the Adverse Event: InForm and Argus Safety integration. Complete the worksheets for the screens before you launch the configuration wizard. For more information, see Chapter 6.
To configure the Adverse Event: InForm and Argus Safety integration:
Navigate to <AIA_Instance>/bin and run the following command, as appropriate for your platform, to configure the installation environment:
Linux: source aiaenv.sh
Windows: aiaenv.bat
Navigate to <AIA_HOME>/bin and run the following command, as appropriate for your platform, to launch the AIA Configuration Wizard:
Linux: ./aiaconfig.sh
Windows: aiaconfig.bat
Click Next.
Expand Core Process Integration Packs in the navigation tree.
Select Adverse Event: InForm and Argus Safety Version 1.0.
Click Next.
To specify Pre-Built Integration Server details:
Enter information for your server in the Pre-built Integration Server Details screen.
Click Next.
To specify Argus Safety details:
Enter information about your Oracle Argus Safety server instance in the Argus Safety Details screen.
Click Next.
To specify InForm and InForm Adapter details:
Enter information about your InForm server in the InForm and InForm Adapter Details screen.
Click Next.
To complete configuration:
Review the configuration information in the Configuration Summary screen.
If you want change the configuration before starting the installation, use the navigation pane on the left and select the topic to edit.
You can also create a response file based on the input provided and use it for future silent installations and deployments.
Click Configure to accept the configuration and begin the installation.
The system displays progress in the Configuration Progress screen.
Warnings or errors are displayed as necessary. You can review the configuration log for additional details. The configuration log location is displayed in the Configuration Progress screen.
Click Next.
When the configuration process completes without errors, the Configuration Complete screen is displayed.
Click Finish to close the configuration wizard.
AIAInstallProperties.xml is updated. This file is located in the <AIA_HOME>/aia_instances/<AIA_instance_name>/config folder. Use this file for deploying the integration pack on the SOA server.
To configure the Adverse Event: InForm and Argus Safety integration using a response file, perform the following steps:
Open the response file.
When you create a response file through the Oracle Universal Installer (OUI), passwords are stored as <SECURE>.
Replace the password fields with actual passwords in the response file.
Navigate to <AIA_Instance>/bin and run the following command, as appropriate for your platform, to configure the environment:
Linux: source aiaenv.sh
Windows: aiaenv.bat
Navigate to <AIA_HOME>/bin and run the following command, as appropriate for your platform:
Linux: ./aiaconfig.sh <Response File Location and Name>
Windows: aiaconfig.bat <Response File Location and Name>
You deploy the Adverse Event: InForm and Argus Safety components on the SOA server as part of the post-installation configurations.
To deploy the integration to the SOA server, run the following commands, as appropriate for your platform.
Navigate to <AIA_HOME/aia_instances/<AIA_instance_name>/bin and enter the following:
Linux: source aiaenv.sh
Windows: aiaenv.bat
Table 7-2 Deployment commands for the InForm - Argus Safety Integration
| Platform | Deployment Command |
|---|---|
|
Linux Solaris SPARC |
ant -f $AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml -DPropertiesFile=$AIA_HOME/aia_instances/<instance_name>/config/AIAInstallProperties.xml -DDeploymentPlan=$AIA_HOME/pips/AEInFormandArgus/DeploymentPlans/AEInFormandArgusDP.xml -DSupplementaryDeploymentPlan=$AIA_HOME/pips/AEInFormandArgus/DeploymentPlans/AEInFormandArgusSupplementaryDP.xml -l $AIA_HOME/pips/AEInFormandArgus/DeploymentPlans/AEInFormandArgus.log |
|
Microsoft Windows |
ant -f %AIA_HOME%\Infrastructure\Install\AID\AIAInstallDriver.xml -DPropertiesFile=%AIA_HOME%\aia_instances\<instance_name>\config\AIAInstallProperties.xml -DDeploymentPlan=%AIA_HOME%\pips\AEInFormandArgus\DeploymentPlans\AEInFormandArgusDP.xml -DSupplementaryDeploymentPlan=%AIA_HOME%\pips\AEInFormandArgus\DeploymentPlans\AEInFormandArgusSupplementaryDP.xml -l %AIA_HOME%\pips\AEInFormandArgus\DeploymentPlans\AEInFormandArgus.log |
AIA ships a few artifacts in AIA Lifecycle Workbench that can be used in your integrations. You can modify these native artifacts, or you can add new, natively supported artifacts using AIA Lifecycle Workbench and then generate a BOM.xml file.
AIA Foundation Pack also supports the deployment of custom artifacts. These artifact types are beyond what is natively supported by Project Lifecycle Workbench and AIA Harvester. For example, you can deploy third party technology artifacts that constitute part of integration landscape in addition to those provided by AIA.
For more information on deploying artifacts, see Oracle® Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 (11.1.1.6.0).
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
