Create a test JMS module as shown in

Index-2 C Callout Directory parameter, 13-7 callouts code example, 13-10 creating, 13-5 creating a library JAR file, 13-5 defining callout JAR file library location, 13-7 definition, 13-1 differently formatted XML messages, 13-3 implementation class, 13-6 implementing, 13-10 including in an agreement, 13-8 library name, 13-7 parameter attributes, 13-7 predefined XSLTCalloutImpl class file, 13-6 transport, 13-3 channel attributes configuring, 5-25 CLIENT-CERT authentication method, 1-5 cloning trading partners, 5-2 command line tools b2bcpaexport, 19-11 b2bcpaimport, 19-11 b2bcreate-cpaprop, 19-9 b2bdeploy, 19-8 b2bexport, 19-6 b2bimport, 19-5 b2bpurge, 19-4 b2bvalidate, 19-9 introduction, 19-1 prerequisites for running, 19-1 configuration parameters, setting, 16-1 control number information, purging, 14-1 conversation report, creating, 17-14 CPPCPA exporting, 19-11 importing, 19-11 templates, creating, 19-9 custom contact information types, creating, 10-4 custom document protocols configuring XPath expressions, 8-6 definition, 8-2 document definition parameters, 8-4 document type parameters, 8-2 document version parameters, 8-2 custom headers extracting, 5-35 custom identifier types, creating, 10-1 custom trading partner parameter types, creating, 10-5 D Data Generator, 3-10 deployed agreement states active, 9-2 changing, 9-4 inactive, 9-2 purged, 9-2 retired, 9-2 deployed agreements managing, 9-2 metrics, 2-8 searching, 9-3 deploying agreements, 19-8 dequeuing See Java dequeue command design metadata, 14-1 design-time repository description, 7-1 exported file, 7-5 exporting, 7-3 importing, 7-2 what is imported or exported, 7-4 document definitions adding, 5-12 changing after importing metadata, 8-41 creating, 2-11, 4-4 definition, 4-1 deleting, 4-9 EDI EDIFACT, 8-9 example, 4-3 trading partner agreements, 6-3 document guidelines available types, 3-2 example, 3-4 document protocols custom, 8-2 definition, 8-1 EDI, 3-2 EDI EDIFACT, 8-9 EDI X12, 4-3, 8-14 EDIEL, 1-3 HL7, 1-2, 1-10, 3-2, 8-19 introduction, 4-2 managing, 2-5 NCPDP Telecom, 1-3, 3-2 OAG, 1-3, 8-25 ParserSchema, 3-2 Partner Interface Process PIP, 8-30 Positional Flat File Document Protocol, 8-27 proprietary transactions, 8-2 RosettaNet, 1-2, 1-3, 1-10, 3-2, 8-29 supported, 1-2 UCCnet, 1-2, 1-3, 8-34 Document Routing IDs, 8-41 document types restricting access, 1-6 DUNS, 10-3 dynamic endpoints, 5-34 E ebMS Identifier, 10-4 ebMS-1.0, 1-3, 5-15, 5-19 ebMS-2.0, 5-15, 5-19 ebXML messaging service ebMS parameters, 8-2 EDI document guidelines, 3-2 Group ID, 10-3 Index-3 Group ID Qualifier, 10-3 Interchange ID, 10-3 Interchange ID Qualifier, 10-3 Interchange Internal ID, 10-3 Interchange Internal Sub ID, 10-3 EDI EDIFACT definition, 8-9 document definition parameters, 8-12 document definitions, 8-9 document protocols, 8-9 document type parameters, 8-11 document version parameters, 8-9 Oracle B2B support, 1-3 samples, 1-10 traditional transaction comparison, 1-2 UNA, 8-10 EDI X12 definition, 8-14 document definition parameters, 8-17 document hierarchy, 4-3 document type parameters, 8-16 document version parameters, 8-14 Oracle B2B support, 1-3 samples, 1-10 traditional transaction comparison, 1-2 EDIEL Oracle B2B support, 1-3 enqueue, JMS JCA adapter, 22-5 enqueuing See Java enqueue command enqueuing and dequeuing, 22-1 error message reports, creating, 17-11 errorDescription, D-2 errorText, D-2 exception handling description, D-1 inbound exception handling scenarios, D-5 inbound messages, D-1 acknowledgement messages, D-2 document identification failure, D-6 document processing failure, D-6 ebMS, AS1, and AS2 failures, D-2 exception messages, D-2 exchange identification failure, D-5 exchange not supported, D-5 message decoding failure, D-5 message duplicated, D-5 message unpacking failure, D-5 request or response messages, D-2 scenarios, D-5 trading partner agreement failure, D-6 outbound messages, D-3 payload definition, D-6 Exception Queue parameter, 16-5, D-3 exchange protocol parameters configuring, 5-27 exporting active agreement, 9-4 CPPCPA files, 19-11 data, 19-6 description, 7-1 design-time repository to file, 7-1 restrictions, 7-1, 9-4 types of export supported, 7-1 F FusionOrderDemo_R1PS1.zip, 2-26 G Generic AQ-1.0, 1-3, 5-15 Generic Email-1.0, 1-3, 5-16 Generic File-1.0, 1-3, 5-15 Generic FTP-1.0, 1-3, 5-15 Generic HTTP-1.0, 1-3, 5-16 Generic Identifier, 10-3 Generic JMS-1.0, 1-3, 5-16 Generic SFTP-1.0, 1-3, 5-15 generic support for TCP, 5-33 H Health Level 7 HL7 Batch Application ID, 10-3 Batch Application Universal ID, 10-3 Batch Application Universal ID Type, 10-3 Batch Facility ID, 10-3 Batch Facility Universal ID, 10-3 Batch Facility Universal ID Type, 10-3 definition, 8-19 document definition parameters, 8-23 document guidelines, 3-2 document type parameters, 8-22 document version parameters, 8-19 File Application ID, 10-3 File Application Universal ID, 10-4 File Application Universal ID Type, 10-4 File Facility ID, 10-4 File Facility Universal ID, 10-4 File Facility Universal ID Type, 10-4 immediate acknowledgment, 8-24 Message Application ID, 10-4 Message Application Universal ID, 10-4 Message Application Universal ID Type, 10-4 Message Facility ID, 10-4 Message Facility Universal ID, 10-4 Message Facility Universal ID Type, 10-4 negative acknowledgment messages, 8-24 Oracle B2B support, 1-3 samples, 1-10 traditional transaction comparison, 1-2 host administrator role, 1-4 host monitor role, 1-4 host trading partner, 5-2 agreements, 6-3 key store information, 5-7 I Identity Store, creating a new user, 5-8