17 Administering Oracle Application Server Integration B2B

Administering OracleAS Integration B2B

Through the user interface tool, you can perform the design tasks shown in Figure 17-1.

Figure 17-1 Design Tasks: Managing Contact Types and Trading Partner Identification Types

Description of "Figure 17-1 Design Tasks: Managing Contact Types and Trading Partner Identification Types"

You can also perform the import, export, and purge management tasks shown in Figure 17-2 using the user interface tool.

Figure 17-2 Management Tasks: Importing, Exporting, and Purging Data

Description of "Figure 17-2 Management Tasks: Importing, Exporting, and Purging Data"

Table 17-1 provides references to instructions for these administration tasks.

Managing Contact Types

This section describes the contact type management tasks shown in Figure 17-1. The contact type is the method for contacting persons or organizations (such as a telephone number or e-mail address). The predefined contact types shown in Figure 17-1 cannot be updated or deleted.

The contact type also appears as a selection on the Organization page (accessible by clicking Partners, then Trading Partners, then trading_partner_name_in_Name_column, then Organization, and then Create). See "Creating Contact Information for a Trading Partner Person or Organization" for more information.

Table 17-2 identifies the contact type management tasks shown in Figure 17-1 and provides references to procedures for performing these tasks.

Managing Trading Partner Identification Types

This section describes the trading partner identification type management tasks shown in Figure 17-1. The trading partner identification type includes a value that uniquely identifies a trading partner, such as a Data Universal Numbering System (DUNS) number or an electronic data interchange (EDI) location code. The predefined trading partner identification types shown in Figure 17-1 cannot be updated or deleted. You can also create your own custom trading partner identification types.

Table 17-3 identifies the trading partner identification type management tasks shown in Figure 17-1 and provides references to procedures for performing these tasks.

Exporting and Importing the Design-Time Repository

The OracleAS Integration B2B user interface tool enables you to create partner data (such as trading partners and trading partner agreements) that is stored in the OracleAS Integration B2B design-time repository portion of the Oracle Application Server Metadata Repository. Partner data is design-time data before it is included in a deployed configuration (for example, trading partner and trading partner agreement data). Partner data is the data that you create under the Partners tab in the Oracle Application Server Integration B2B user interface tool.

The OracleAS Integration B2B user interface tool provides design-time repository export and import functionality that enables you to perform several tasks, including the following:

• Export and import the entire contents of the design-time repository to and from an XML file. This enables you to export the contents from one repository and import it into another repository.

• Export and import a configuration created under the Deployment tab to and from the design-time repository

• Import supported, predefined RosettaNet collaborations (partner interface processes (PIPs)), EDI X12 and EDI EDIFACT transaction sets (business actions), and UCCnet standards into the design-time repository to assign to trading partners. This information can then be viewed by clicking Partners, then Protocols, then business_protocol_name_in_Name_column, then Process Protocol Revisions, and then Details. A transaction set maps to a document type of a business action in the OracleAS Integration B2B user interface tool.

There are several methods for using export and import.

• In high availability environments, you can back up specific configurations from your design-time repository.

• For migrating from a test environment to a production environment, you can import configurations tested in a staging environment into a production environment.

  OracleAS Integration B2B supports the following types of export:

  • The export feature accessible under the Administration tab (and described in this section) exports the latest versions of all partner data in the design-time repository to a file.

  • The configuration export feature accessible under the Deployment tab exports only the data included in a specific configuration.

  • The export feature accessible from the Agreement Details page and Trading Partner Details page exports the partner data associated with those pages to XML files. The XSDs for these XML files are included in the exported document.

  Note the following details about importing and exporting the latest versions of all partner data to a file:

  • The wallet password for the host trading partner is not exported or imported. This password must be created manually by following the instructions under Partners, then Trading Partners, and then host_trading_partner_name_in_Name_column.

  • All trading partner agreements are imported in the Draft state, even if they were approved before the export. You must validate the relevant trading partner agreements before creating and deploying a configuration.

  • Do not use the OracleAS Integration B2B export and import features for backup or recovery of the design-time repository. OracleAS Integration B2B uses the b2b schema in the metadata repository. This schema has additional metadata and run-time state not included in the OracleAS Integration B2B export file. Use the Oracle database import and export utilities or the Oracle Application Server archiving tool to back up this schema.

  Table 17-4 identifies the management tasks you can perform from the Management tab main page and provides references for performing these tasks.

  Table 17-4 Management Tasks

  Management Task	See Section...
  Export the entire design-time repository to a file	"Exporting the Design-Time Repository Contents"
  Import the design-time repository from a file (exported by clicking Administration, then Management, and then Export)	"Importing the Design-Time Repository Contents"
  Import a configuration (exported by clicking Deployment, then configuration_name_in_Name_column, and then Export)	"Importing an Exported Configuration"
  Import supported, predefined RosettaNet collaborations, EDI transaction sets, and UCCnet standards	"Importing Support for Collaborations, Transaction Sets, and UCCnet Standards"

  
  

See the following for more information:

• "Exporting a Configuration" for instructions on exporting a configuration

• "Exporting Partner Data to an XML File" for instructions on exporting partner data to a file

• "Managing Trading Partner Persons" for instructions on creating persons and assigning passwords

• "Managing the Host Trading Partner Wallet Password" for instructions on creating a wallet password for the host trading partner

• Oracle Application Server Administrator's Guide for details about Oracle Application Server backup and recovery

• Oracle Database Backup and Recovery Basics, available on the Oracle Technology Network Web site at

  http://www.oracle.com/technology
  

The Run-Time Repository

The OracleAS Integration B2B runtime repository stores instance data. Instance data is partner data included in a deployed configuration. During configuration creation, partner data of the integration is validated end-to-end a final time to ensure that only a complete and consistent configuration is deployed to the runtime repository. After a configuration is deployed, the runtime repository stores the configuration of instance data required to execute an integration. Instance data is created during run time when messages are processed.

Purging the Entire Repository

The entire repository—the Oracle Application Server Metadata Repository—contains contains design-time configuration (partner) data, run-time configuration data, and run-time instance data.The OracleAS Integration B2B user interface tool enables you to purge the entire repository, with the exception of the host trading partner name, which is not purged. Predefined data that was part of the installation (for example, business protocols such as EDI and RosettaNet and identification types such as a Data Universal Numbering System (DUNS) and an EDI Location Code) is not deleted.

Purging enables you to perform the following tasks:

• Manage disk space and improve performance

• Delete multiple objects of larger granularity

To purge the entire repository:

1. Click Administration, then Management, and then Purge.

2. Click Entire Repository, then Purge.

   The Business Messages and Collaboration Instances options are not available. See "Purging Business Messages and Wire Messages Using the Purge Utility" for more information.

   The message Purging will permanently remove the data and user should archive the data using Oracle DB archive features for future reference. Are you sure you want to purge entire repository? appears.

3. Click Yes.

Purging Business Messages and Wire Messages Using the Purge Utility

OracleAS Integration B2B provides a command-line utility to purge business messages and wire messages from the repository, based on specified criteria. You can run the command in both interactive and noninteractive modes. Noninteractive mode runs much faster than interactive mode.

In interactive mode, the utility prompts you for the start and end dates (inclusive) of the messages to be purged. The number of messages to be purged is displayed. The purge begins after your confirmation.

To run the purge utility in interactive mode:

$ java oracle.tip.adapter.b2b.purge.Purge

In noninteractive mode, you invoke this utility from a shell script or as a cron job. The utility does not prompt for your confirmation.

To run the purge utility in noninteractive mode:

$ java oracle.tip.repos.purge.PurgeManager -purgeRuntime -start mm/dd/yyyy -end mmm/dd/yyyy

The start and end arguments are the inclusive dates of the messages to be purged.

Common User Errors

• Do not manually edit exported files. If you do so, OracleAS Integration B2B cannot guarantee their integrity.

Chapter Summary

This chapter describes how to use the OracleAS Integration B2B user interface tool for the following tasks:

• Manage contact types and trading partner identification types

• Export and import the design-time repository to and from XML files

• Import configurations from XML files

• Import collaborations, transaction sets, and standards

• Purge the entire repository

• Purge business messages and wire messages using the purge utility