Skip Headers
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.1

E36158-02
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

9 Verifying Installation

To verify the Adverse Event: InForm and Argus Safety installation:

  1. Open the log files from the following location and look for warnings and error messages:

    • For Linux and Solaris SPARC based systems: Review the install log located at <AIA_HOME>/aia_instances/<AIA_Instance_name>/logs to verify that the integration is successfully installed.

    • For Windows: Review the install log located at <AIA_HOME>\aia_instances\<AIA_Instance_name>\logs to verify that the integration is successfully installed.

  2. Confirm that the Oracle Health Sciences InForm and Oracle Argus Safety Integration components were successfully installed.

    1. Navigate to the EM Console:

      http://<server name>:<port number>/em/

    2. Log in with the server admin user name. For access details, contact the system administrator.

    3. Navigate to soa-infra/services/default and look for items listed below.

      • HealthSciencesDrugSafetyReportEBS

      • HealthSciencesDrugSafetyReportResponseEBS

      • InFormDrugSafetyReportJMSProducer

      • InFormDrugSafetyReportJMSConsumer

      • ReportDrugSafetyReportInFormReqABCSImpl

      • ReportDrugSafetyReportArgusProvABCSImpl

      • ReportDrugSafetyReportWriteE2BFileAdapter

      • ReportDrugSafetyReportReadAckFileAdapter

      • ReportDrugSafetyReportResponseArgusReqABCSImpl

      • ReportDrugSafetyReportResponseInFormProvABCSImpl

9.1 Validating Security Policies

This integration pack fully leverages the security infrastructure provided by the Oracle 11g SOA Suite, AIA Foundation Pack, and the underlying transport layer security features for Web Service security. This is implemented through Foundation Pack by assigning global service and client security policies that use user name or SAML tokens for authentication. These global policies are automatically assigned during deployment of the AIA services.

The global server policy name is oracle/aia_wss_saml_or_username_token_service_policy_OPT_ON and the global client policy name is oracle/aia_wss10_saml_token_client_policy_OPT_ON.

9.1.1 Verifying the Security Policies

To verify the security policies, perform the following:

  1. Navigate to the WebLogic EM Console: http://<server name>:<port number>/em/.

  2. Log in with the server admin user name. For access details, contact the system administrator.

  3. Navigate to Farm_soa_domain > SOA > soa-infra(<managed server name>) > default (<service_name>).

    The default managed server name is soa_server1.

  4. Select an integration pack service for which security policy needs to be verified.

  5. On the right hand side, select Policies.

  6. Verify the security policy listed in the following table is applied for the service.

9.1.2 Policy Applied for Services Deployed

Refer to Table 9-1 for verifying the security policies.

By default, AIA applies global policies. Local policies will override global policies, where applicable.

For more information about security validation, see Oracle® Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack 11g Release 1 (11.1.1.6.0).

For Adverse Event: InForm and Argus Safety implementation, see Oracle Health Sciences Adverse Event Integration Pack for InForm and Oracle Argus Safety 1.0 Implementation Guide.

Table 9-1 Security Policies

Service Name Policy Name

ReportDrugSafetyReportResponseInFormProvABCSImpl

oracle/wss_username_token_client_policy is locally applied on Safety reference.