Managing Oracle WebLogic Integration Solutions

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Using the Trading Partner Bulk Loader

The Bulk Loader is a command line tool that you can use to import, export, and delete trading partner management (TPM) data. This data includes trading partner profiles, certificates from keystores, service definitions, and service profiles. The Bulk Loader imports an XML representation of TPM data and it exports to an XML file. Validation of the XML input documents is performed using the XSD schemas. The Bulk Loader uses an XML configuration file (blconfig.xml) to obtain parameters for connecting to the database and certificate keystores. If the Bulk Loader detects any errors during this procedure, it creates an error log.

The following sections provide information on using the Bulk Loader:

 

About Using the Bulk Loader

The Bulk Loader command line tool should only be used when the Oracle WebLogic Integration server is not running. If the Oracle WebLogic Integration server is running, all configuration changes to TPM data in the database should be performed through the Oracle WebLogic Integration Administration Console. The Oracle WebLogic Integration Administration Console also supports import, export, and bulk delete operations. Using the Oracle WebLogic Integration Administration Console for these operations ensures that the running servers in a Oracle WebLogic Integration domain have consistent TPM data in their internal TPM memory cache.

For more information, see the following sections in Using the Oracle WebLogic Integration Administration Console.

 

Schemas

When importing and exporting repository data and trading partner configuration, two XSD schemas are used by the Bulk Loader to validate the imported or exported XML documents. The TPM.xsd, which specifies the trading partner information and the BulkLoaderConfig.xsd, which specifies database and keystore information and the transaction processing options. These schemas are based on the 2001 XML Schema Definition (XSD).

Both the TPM.xsd and BulkLoaderConfig.xsd schemas are in the schema/src directory inside the jpd.jar file. These files are located in the following directory:

BEA_HOME\wli_10.2\lib

BEA_HOME represents the home directory.

To learn about the entities and elements that comprise trading partner management data in the TPM.xsd file, see Trading Partner Management Schema.

To learn about setting up keystore information and the transaction processing options in the BulkLoaderConfig.xsd, see Transaction Processing Options and Importing or Exporting Certificate Elements.

 

Configuring the Bulk Loader Configuration File

The Bulk Loader uses a configuration file (blconfig.xml) to get parameters for connecting to the database and certificate keystores. Before using the Bulk Loader, you must modify this file to match your database installation.

The blconfig.xml configuration file is located in the following directory:

BEA_HOME\wli_102\bin

BEA_HOME represents the home directory.

Listing 5-1 blconfig.xml

<?xml version="1.0" encoding="UTF-8"?>
<bulkloader-config
xmlns="http://www.bea.com/2003/03/wli/tpm/bulkloader"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/2003/03/wli/tpm/bulkloader BulkLoaderConfig.xsd">
<database-info>
<!-- Modify the following to match your database installation -->
<url>jdbc:pointbase://localhost:9093/workshop</url>
<driver>com.pointbase.jdbc.jdbcUniversalDriver</driver>
<userid>weblogic</userid>
<password>weblogic</password>
</database-info>
<encoding>UTF-8</encoding>
</bulkloader-config>

 

Using the Bulk Loader Command Line Options

The Bulk Loader is located in the following directory:

BEA_HOME\wli_102\bin

In the preceding line BEA_HOME represents the home directory.

The Bulk Loader usage is as follows:

bulkloader [-verbose] [-config <blconfig.xml>] [-wlibc]

-import <data.xml>

-export <data.xml> [-nokeyinfo] [-select <selector.xml>]

-delete <selector.xml>

Table 5-1 summarizes the options for the Bulk Loader commands.

Table 5-1 Bulk Loader Commands
Option
Description
[-verbose]
Optional. Use verbose mode to help you troubleshoot problems in your import, export, or delete process.
[-config <blconfig.xml>]
Optional. Use to designate an explicit configuration file. Default is blconfig.xml. If not using the default, specify the full path of the configuration file.
-import <data.xml>
Use to import data. Specify the full path of the TPM file you want to import.
To learn more about importing, see Importing and Exporting Trading Partner Management Data.
-export <data.xml>
[-nokeyinfo]
[-select <selector.xml>]
Use to export data. Specify the full path of the TPM file you want to export.
The [-nokeyinfo] option suppresses export of KeyInfo elements for trading partner certificates.
The -select option specifies the selector file and selector.xml specifies the type of data to be exported. You can use the selector.xml file to export all or just selected Trading Partners. This file can also designate that all or selected Services for export. This file must conform to the TPM.xsd schema.
To learn more about exporting, see Importing and Exporting Trading Partner Management Data.
-delete <selector.xml>
Use to delete data. Specify the full path of the TPM file used for selecting the elements to be deleted.
Use selector.xml to specify the elements that you want to delete. This file must conforms to the TPM.xsd schema.
To learn more about deleting, see Deleting Management Data.

 

Importing and Exporting Trading Partner Management Data

You can import or export trading partner management information including certificate data using the Bulk Loader. The Bulk Loader imports an XML representation of the TPM data and it exports an XML file. Before importing or exporting certificates you need to modify the blconfig.xml file as described in Importing or Exporting Certificate Elements. How to import and export trading partner information is described in the following topics:

Transaction Processing Options

In case of errors or when working with large repositories, you can use two attributes contained in the BulkLoaderConfig.xsd schema to control transaction processing. These attributes are transaction-level="all" and transaction-level="default". They are under the <bulkloader-config> root element. These options provide the same functionality available in the Oracle WebLogic Integration Administration Console.

The attribute transaction-level="all" performs the following:

The attribute transaction-level="default" performs the following:

General Procedure for Importing and Exporting

This section contains information about importing and exporting trading partner management data.

To import or export trading partner management data:

Before importing or exporting a TPM file, ensure that the TPM file conforms to the TPM.xsd schema.

  1. On a Windows system, open a command window.
  2. In both Windows and UNIX, go to the following directory: 
    3. BEA_HOME\wli_102\bin

    In the preceding line, BEA_HOME represents the home directory.

  3. Execute the import or export by entering the appropriate commands:
    4. bulkloader [-verbose] [-config <blconfig.xml>] [-wlibc]
    -import <data.xml>
    -export <data.xml> [-nokeyinfo] [-select <selector.xml>]

The following shows an example of importing a trading partner XML file. 

bulkloader -wlibc -import d:\tradingpartners\profiles\WorldWideTrading.xml

This example shows exporting services offered by a remote trading partner: 

bulkloader -config myconfig.xml -export exports\NationalTradingServices.xml -select selectors\NationalTradingSelector.xml

Importing or Exporting Certificate Elements

Note: Only the certificates for remote Trading Partners can be imported; certificates for local Trading Partners cannot be imported.

Importing and exporting of certificates, as with other trading partner profile information, is done in XML format. The XML representation of the certificates conforms to the certificate representation format specified in the W3C XML-Signature Syntax and Processing recommendation, which is available at the following URL:

http://www.w3.org/TR/xmldsig-core/#sec-KeyInfo

The Bulk Loader only supports import or export of certificate data and public keys. The Private Key of certificates is not imported or exported; an administrator must manually perform the transfer of the Private Key. The keystore related information is read from the Bulk Loader configuration file (blconfig.xml).

Note: To learn more about the Oracle WebLogic Server Keystore, see “ WebLogic Keystore Provider-->General” in the Oracle WebLogic Integration Administration Console Online Help.

When the input XML file has certificate elements for a trading partner with <ds:KeyInfo> sub-elements, the specified certificate-key data is added to the appropriate keystore as designated by the Bulk Loader configuration file.

The Bulk Loader configuration schema (BulkLoaderConfig.xsd) includes keystore configuration information. This is an optional element in the schema. The following extract is from the schema definition for the keystore-info element: 

<xs:element name="keystore-info">  
  <xs:complexType>  
   <xs:sequence>  
    <xs:element name="path" type="xs:string"/>  
    <xs:element name="password" type="xs:string"/>  
   </xs:sequence>  
  </xs:complexType>  
 </xs:element>  
 <xs:element name="encoding" type="xs:string"/>

Passwords for the database and keystore can be initially entered in the blconfig.xml file in clear text. After the operation successfully completes, the Bulk Loader encrypts the passwords and re-writes the blconfig.xml file with the encrypted form of the passwords.

The path element is the absolute file path to the Java KeyStore. The password element is the keystore password.

The following is an example of the Bulk Loader configuration file that includes keystore information.

Listing 5-2 blconfig.xml with Keystore Information 
<?xml version="1.0" encoding="UTF-8"?>
<bulkloader-config
    xmlns="http://www.bea.com/2003/03/wli/tpm/bulkloader"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/2003/03/wli/tpm/bulkloader
    BulkLoaderConfig.xsd">
  <database-info>
    <url>jdbc:pointbase://localhost:9094/WLIDB</url>
    <driver>com.pointbase.jdbc.jdbcUniversalDriver</driver>
    <userid>PBPUBLIC</userid>
    <password>PBPUBLIC</password>
  </database-info>
  <keystore-info>
    <path>D:\test\peer1KeyStore.pks</path>
    <password>peer1<password>
  </keystore-info>
</bulkloader-config>

The following is an example of trading partner information with a client certificate in import-export format.

Listing 5-3 Trading Partner with Client Certificate 
<trading-partner
  name="ebxml-sender"
  type="REMOTE"
  status="ENABLED">
  <client-certificate name="peer1-en">

<KeyInfo>
  <KeyName>1.2.840.113549.1.9.1=#160d7065657231406265612e636f6d,
    CN=localhost.peer1-en.crt,OU=ECI Division,O=BEA Systems,
    ST=California,C=US
  </KeyName>
  <KeyValue>
    <RSAKeyValue>
      <Modulus>t/kDK6Jezk2e31k2nMQMagPuXsC56df18YW0KRqQa89Q7o/
        H8O8m6LdOH5H0GyYEUBD+jN08lgZqCQMDAZCG6w==</Modulus>
      <Exponent>AQAB</Exponent>
    </RSAKeyValue>
  </KeyValue>
  <X509Data>
  <X509SubjectName>1.2.840.113549.1.9.1=#160d7065657231406265612e636f6d,
    CN=localhost.peer1-en.crt,OU=ECI Division,O=BEA Systems,
    ST=California,C=US</X509SubjectName>
  <X509IssuerSerial>
<X509IssuerName>1.2.840.113549.1.9.1=#1610676172696d656c73406265612e636f6,
  CN=luke.bea.com,OU=WLC Luke,O=ECI Division\, BEA Systems Inc,
  L=San Jose,ST=California,C=US</X509IssuerName>
    <X509SerialNumber>DQ==</X509SerialNumber>
  </X509IssuerSerial>
<X509Certificate>MIICQzCCAe2gAwIBAgIBDTANBgkqhkiG9w0BAQQFADCBqDELMAkGA1UEB
hMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExETAPBgNVBAcTCFNhbiBKb3NlMSYwJAYDVQQKEx1
FQ0kgRGl2aXNpb24sIEJFQSBTeXN0ZW1zIEluYzERMA8GA1UECxMIV0xDIEx1a2UxFTATBgNVB
AMTDGx1a2UuYmVhLmNvbTEfMB0GCSqGSIb3DQEJARYQZ2FyaW1lbHNAYmVhLmNvbTAeFw0wMjA
xMDEwMDAwMDBaFw0wMzAxMDEwMDAwMDBaMIGOMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2Fsa
WZvcm5pYTEUMBIGA1UEChMLQkVBIFN5c3RlbXMxFTATBgNVBAsTDEVDSSBEaXZpc2lvbjEfMB0
GA1UEAxMWbG9jYWxob3N0LnBlZXIxLWVuLmNydDEcMBoGCSqGSIb3DQEJARYNcGVlcjFAYmVhL
mNvbTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgCQQC3+QMrol7OTZ7fWTacxAxqA+5ewLnp1/XxhbQ
pGpBrz1Duj8fw7ybot04fkfQbJgRQEP6M3TyWBmoJAwMBkIbrAgMBAAGjGjAYMAkGA1UdEwQCM
AAwCwYDVR0PBAQDAgXgMA0GCSqGSIb3DQEBBAUAA0EAA8QAs20bOFvebMd6mU6ui7lAYZd+5+d
OhTU0R03VgY35ZQXzyaOH7GtMHNOomFqKaRdckwAi75FZTuAfKVYJfw==
</X509Certificate>
  </X509Data>
</KeyInfo>

  </client-certificate>
</trading-partner>

 

Deleting Management Data

The Bulk Loader provides the ability to bulk delete management data. The delete operation removes trading partners information based on an input selector file. It deletes each selected leaf element and all linked child elements associated with that element. For example, if you delete a particular Trading Partner from the repository, all child certificate, binding, transport, and authentication elements are also deleted.

To delete management data using the Bulk Loader:
  1. Create an input file that specifies the data elements to be deleted from the repository, as shown in the following example.

    2. TpmDelete.xml 

    <?xml version="1.0" encoding="UTF-8"?>
    <trading-partner-management
        xmlns="http://www.bea.com/2003/03/wli/tpm"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.bea.com/2003/03/wli/tpm TPM.xsd">
        … elements to be deleted are specified here in XML …
    </trading-partner-management>
  2. On a Windows system, open a command window.
  3. In both Windows and UNIX, go to the following directory: 
    4. BEA_HOME\wli_10.2\bin

    In the preceding line, BEA_HOME represents the home directory.

  4. Execute the bulk delete by entering:
    5. bulkloader [-verbose] [-config <blconfig.xml>] [-wlibc] -delete <selector.xml>

    For a description of these options, see Table 5-1.


  Back to Top       Previous  Next