Implementing a Callout Oracle Fusion Middleware Online Documentation Library

14 Purging Data 14-1 14 Purging Data Use the Oracle B2B interface to purge design metadata and instance data. This chapter contains the following topics: ■ Section 14.1, Purging Design Metadata and Instance Data See the following for alternate methods of purging: ■ Chapter 19, B2B Command-Line Tools

14.1 Purging Design Metadata and Instance Data

Use the Oracle B2B interface to purge design metadata and instance data. Design metadata contains partner profile data, identifiers, document definitions, channels, and agreements. When you purge this data, predefined data that is part of the installation the host trading partner name, protocols, and identification types, for example is not purged. Instance data is created during run time when messages are processed. Instance, or run-time, data contains the business messages and message-related data. Specific instance data can be purged from the Business Message tab of the Reports link. See Section 17.1.2, Purging Messages, for more information. Purging does not remove artifacts that B2B creates in the Credential Store, such as passwords. See Oracle Fusion Middleware Security Guide for more information about the Credential Store. With an instance message purge, you can optionally purge control number information. Control numbers are used in EDI X12 and EDIFACT and HL7 message standards. B2B keeps track of control numbers for inbound and outbound messages. For outbound messages, B2B generates the control numbers in a sequence from an internal control number table. Because purging instance data and control numbers resets the sequence the control number table is reset, an outbound message after a purge may have the same control number as a message before the purge. If this is undesirable, do not purge control numbers. Purging is useful for: ■ Managing disk space and improving performance ■ Removing repositories on a test system Caution: Archiving is required before purging data. Purging is an irreversible operation. Ensure that you first archive any important data. 14-2 Oracle Fusion Middleware Users Guide for Oracle B2B To purge design metadata or instance data: 1. Click the Administration tab, and then the Purge tab. 2. Optional if purging instance data. Select Purge Control Number to reset the sequence.

3. Click Purge Design Metadata or Purge Instance Data, as shown in

Figure 14–1 . Figure 14–1 Purging Design Metadata or Instance Data The image shows the Purge tab, which displays the Purge Design Metadata button and the Purge Instance Metadata button. The Purge Instance Metadata button is inaccurate. It should be labeled Purge Instance Data. The Purge Control Number checkbox is also displayed. If you select Purge Design Metadata, then the message Do you want to delete all the design metadata from the repository permanently? appears. If you select Purge Instance Data, then the message Do you want to delete all the runtime data from the repository permanently? appears.

4. Click Yes.

15 Configuring Listening Channels 15-1 15 Configuring Listening Channels A listening channel is used to send messages to Oracle B2B. A listening channel listens on an endpoint for messages. If a listening channel is marked as internal, then it can be used by any internal business application. If it is used as an external channel, then any trading partner can send a message to Oracle B2B using this channel. This chapter contains the following topics: ■ Section 15.1, Adding a Listening Channel and Protocol ■ Section 15.2, Using Transport Protocols ■ Section 15.3, Adding Listening Channel Details ■ Section 15.4, Configuring a Listening Channel ■ Section 15.5, Configuring Document Sequencing

15.1 Adding a Listening Channel and Protocol

Listening channels are used globally. You do not need to select a listening delivery channel in an agreement. Listening channels are used for any trading partner to send inbound messages to Oracle B2B or for any back-end business application to send outbound messages to Oracle B2B. When you add a listening channel, you also specify the protocol that the channel uses, as shown in Figure 15–1 . 15-2 Oracle Fusion Middleware Users Guide for Oracle B2B Figure 15–1 Adding a Protocol for a Listening Channel The image shows the following tabs on the Oracle B2B screen: Schedule Batch, Manage Batch, Callout, Purge, Listening Channel, and Configuration. The Listening Channel tab is selected. The first area of the tab shows the Listening Channel list as a table with the following columns: Name and Protocol. The second area of the tab shows the Channel Details and displays the Transport Protocol field a drop-down list. The third area of the tab shows the following sub-tabs: Transport Protocol Parameters, Channel Attributes, Exchange Protocol Parameters, and Security. The Transport Protocol Parameters tab is selected and shows the following fields: Host name, Password, ConfirmPassword, User name, Send as attachment, Folder, Email Id, and Subject. By using a global listening channel, you can keep all messages in one directory from which Oracle B2B pulls. This approach is useful for File, FTP, and SFTP SSH FTP exchanges. Table 15–1 describes the listening channel protocols supported by Oracle B2B.