| Oracle® Argus Safety Installation Guide Release 8.1 E71757-01 |
|
 Previous |
 Next |
This chapter lists the steps to configure Oracle B2B as per your requirements.
|
Note: Either Oracle B2B or Axway Synchrony is required for E2B reports exchange. Customers can choose any one of the software, as required. |
This section lists the steps to integrate Argus Safety with Oracle B2B, if the latter is selected as the EDI Gateway.
The entire integration process can broadly be categorized under the following steps:
Creation of integration tables in B2B Schema through provided scripts
Oracle B2B UI Configuration
General configuration
Document configuration
Enterprise Manager Configuration
SOA Composites deployment
SOA Composites configuration
Web Logic Console configuration
Data Sources and JNDI configuration
Large Payload configuration
Configuration on Argus Safety side
There are a few database objects which are created in ESM Schema for outbound files integration as part of Argus Safety installation. However a few database objects need to be created in B2B Schema for inbound files integration.
After Argus Safety is installed, locate DB Script B2B_setup.bat under %Argus Installation Folder%\Oracle\Argus\DBInstaller\Utilities\B2B_Setup\. Double click it to provide database details of B2B. This is recommended to be installed under SOA_INFRA Schema of B2B database instance.
This script creates 2 database objects required to integrate incoming files data:
B2B_ARGUSSAFETY_INBOUND (table)
S_B2B_ARGUSSAFETY_INBOUND (sequence)
Log in to Oracle B2B UI as an admin user.
Follow the steps listed below:
Under the Non Purgeable section, set Use JMS Queue as default to True.
Under the Miscellaneous section, set Additional MIME Types to application/octet-stream : application/pdf.
Under the Performance section, set Large Payload Directory to the desired location. It is recommended to set it, even if large payloads are not likely to be received.
There can be one document type configured for each of the following categories, as transmitted and received from Argus Safety:
XML - for E2B Message and Acknowledgments
SGML files with no EDI Header and Footer are also categorized under this category.
Zip - for PMDA E2B Message files
PDF - for E2B R2 Attachments
The Zip and PDF may be combined together under one category since both are binary documents. One common doc type may be sufficient for them.
EDI files - for those E2B Reporting Destinations in Argus Console for which EDI Header and footer is checked. If there is no such Reporting Destination, this document type need not be created. Identification Types for EDI Files can be given as:
Identification Start Position = 1
Identification End Position = 3
Identification Value = UNB
Besides this, XML, EDI, and Binary should be created as separate document types rather than as different document definitions under one document type.
There are 2 composites provided with the Argus Safety build to integrate Oracle B2B, one is for all outbound traffic from Argus Safety, sca_AS_BPEL_Outbound_rev1.0.jar. The other one is for all inbound traffic to Argus Safety, sca_AS_BPEL_Inbound_rev1.0.jar. The location of the files is \Support\OracleB2B in the installation directory.
Log in to Enterprise Manager with Admin user.
Locate the domain under which composites are to be deployed.
Right-click and select SOA Deployment > Deploy To This Partition.
Select the path of the JAR file and click Next to deploy the JAR file.
Repeat the above process to deploy the other JAR file.
There are certain parameters for the deployed composites which need to be modified as per Customer Environment.
Right-click on AS_BPEL_Outbound under the deployed domain in Enterprise Manager and click on Service/Reference Properties.
Select AS_FileAdapter.
Change PhysicalDirectory and PhysicalArchiveDirectory to the desired location. The other properties are not supposed to be changed.
Argus Safety may create outbound files under the same or under any of the child directories of the above specified directory.
B2B_DBAdapter should NOT be changed for any of the properties.
B2B_JMSAdapter can be changed, but only if required.
Right-click on AS_BPEL_Inbound under the deployed domain in Enterprise Manager and click on Service/Reference Properties.
Select AS_FileAdapter.
PhysicalDirectory should be set as the top level folder under which all the incoming files are dropped by B2B.
The other properties are not supposed to be changed.
Select LargeFileReader.
The PhysicalDirectory should be the same as Large Payload Directory under Oracle B2B UI > Administration > Configuration > Performance section.
The other properties are not supposed to be changed.
B2B_DBAdapter should NOT be changed for any of the properties.
B2B_Inbound can be changed, but only if required.
Log in to Web Logic Console to create the following data sources and JNDI configuration:
This is hard coded JNDI Identifier being used inside AS_BPEL_Outbound SOA Composite for outbound files. This should point to a data source which has all access to Argus Safety database table B2B_ARGUSSAFETY_OUTBOUND under ESM Schema. This table is available as part of Argus Safety installation.
The configuration has been validated with xADataSource property filled with a data source using database driver as 'Oracle's Driver (Thin XA) for instance connection; Version: 9.0.1 and later'.
This is a hard coded data source being used inside AS_BPEL_Inbound SOA composite for inbound files. This should point to data source which has access all access on integration database table B2B_ARGUSSAFETY_INBOUND and sequence S_B2B_ARGUSSAFETY_INBOUND. These are created as part of script.
Besides this, the same data source can be used as underlying data source under the following:
The configuration has been validated with database driver chosen as "Oracle's Driver (Thin XA) for instance connection; Version:9.0.1 and later".
This is hard coded JNDI Identifier being used inside sca_AS_BPEL_Inbound_rev1.0.jar for inbound files. This should point to data source which has access all access on B2B database table B2B_ARGUSSAFETY_INBOUND and for Sequence S_B2B_ARGUSSAFETY_INBOUND created under the step above "Creation of integration tables in B2B Schema".
The data source created in the above section "jdbc/ArgusSafety_Inbound" can be used as a data source here.
The configuration has been validated with xADataSource property filled with a data source using database driver as "Oracle's Driver (Thin XA) for instance connection; Version: 9.0.1 and later".
Navigate to Deployments >Summary of Deployments >DbAdapter > Configuration > Outbound Connection Pools, and verify that the DB Adapters are present for the data sources created in the Section 8.1.4.1, "Data source with JNDI Name as 'eis/DB/ArgusSafety_Outbound'," and Section 8.1.4.3, "Data source with JNDI Name as 'eis/DB/ArgusSafety_Inbound'".
Make sure that Data Source Name (JNDI Name) has been configured in the property 'XADataSourceName'. If not present, then create a data source with the name 'eis/DB/ArgusSafety_Outbound' and 'eis/DB/ArgusSafety_Inbound' respectively for the corresponding data sources name populated in 'XADataSourceName'.
For B2B, a large payload is a file bigger than the configured size on B2B UI > Administration > Configuration > Performance section. Argus Safety can send large files if E2B R2 Attachments are configured or E2B R3 or eVAERS files are exchanged. With other scenarios generally large payloads may not be applicable. Each following point specifies if they are needed even if you are exchanging small files.
Select Trading Partner > Channel > Channel Attributes > Ack Mode to be Async. This configuration is good even if large payloads are not supposed to be exchanged.
Log in to Enterprise Manager.
Go to SOA > (Domain) > SOA Administration > B2B Server Properties.
On the right side, under the Operation tab, click addProperty to add a new property called b2b.setisLargePayloadPropertyForSmallMsg with value as True.
The Large Payload Directory configuration should be the same for B2B Web UI > Administration > Configuration > Performance section, and also for Enterprise Manager > SOA > (Domain) > AS_BPEL_INBOUND > LargeFileReader PhysicalDirectory porperty.
Both these configurations are required, even if large payloads are not expected to be exchanged.
Log in to Web Logic Console > (Domain) > Services > JTA > Timeout Seconds. This can be set to 720 seconds to allow processing of large pay loads. This has been tested with 20 MB files.
This may have to be tuned if transaction time out errors occur for the same size or larger size files.
This section comprises the following sub-sections:
Configure Oracle B2B
Update for B2B Documents
Argus Console > Reporting Destination Code List
Log in to ESM Mapping Utility as an ESM Admin user.
Go to Administrator Menu > Setup INI file > EDI Section.
Select Oracle B2B as the EDI Gateway. The Oracle B2B database details should be provided for a User who has all access on the following:
B2B_ARGUSSAFETY_INBOUND table (all access)
B2B_INSTANCEMESSAGE table (read access)
Document configuration, as mentioned under Oracle B2B UI > Configuration > Document should be updated in Argus Safety by manually updating the database table B2B_ARGUSSAFETY_DOC under ESM Schema of Argus Safety.
| Doc_ID | Doc_Type | Doc_Revision | Comments (Not a column) |
|---|---|---|---|
| 1 | AS_XmlDoc | ArgusSafety_1.0 | Xml for E2B Message and Acknowledgments |
| 2 | AS_BinaryDoc | ArgusSafety_1.0 | Zip for PMDA E2B Message files |
| 3 | AS_BinaryDoc | ArgusSafety_1.0 | PDF for E2B Attachments |
| 4 | AS_EDIDoc | ArgusSafety_1.0 | EDI files |
The above is the sample factory data provided. The Admin is expected to update only Doc_Type and Doc_Revision columns from Doc Type and Doc Revision information respectively from B2B UI.
The Doc ID column must not be updated and new Doc Id is not supported.
Besides this, the mapping between Doc Id and other columns is assumed to be exactly as provided in the sample above. Example: Doc_ID = 1 should not point to Binary Docs.
Doc ID = 2 and Doc ID = 3 can point to the same or different doc type and doc version but neither of these should be left blank.
If there is no Reporting Destination with EDI Header and Footer configuration, Doc_ID=4 may be left blank.
This information is picked up by outbound SOA Composite at run time to dynamically attach Document Type and Document Version properties to outgoing file via JMS.
