Enqueue—Using a JMS JCA Adapter or Custom Utilities JMS Dequeue
e. In the Remote JNDI Name field, enter Queuesqueue_name if the
destination is a queue, or enter Topicstopic_name if the destination is a topic. For example, the default name for an AQ queue created for the Oracle B2B - Oracle BAM integration is QueuesB2B_BAM_QUEUE.f. Click OK.
7. Restart Oracle WebLogic Server.23.4 Create a B2B Data Object using Oracle BAM Architect
To create a B2B data object: 1. Log in to Oracle BAM at the following URL: http:host_name:port_numberOracleBAM The default port number is 9001.2. Select Architect to open the Oracle BAM Architect application.
3. Select Data Objects in the drop down list.
4. Select the Samples folder, and create a subfolder named B2B.
5. Click on the Create Data Object link
6. Enter B2BDO in the Name field.
7. Click Add a Field.
8. Enter values for Fields in Data Object.
9. Repeat, clicking Add a Field to add all fields as listed in
Table 23–2 . For more information about creating Oracle BAM data objects, see Defining and Managing Oracle BAM Data Objects in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.23.5 Define a JMS Message Source Using an Oracle BAM Enterprise Message Source
To define a JMS message source: 1. Log in to Oracle BAM at the following URL: http:host_name:port_numberOracleBAM The default port number is 9001.2. Select Architect to open the Oracle BAM Architect application.
3. Select Enterprise Message Sources in the drop down list.
4. Click Create, and enter the Enterprise Message Source information for AQ JMS
Queue as indicated in Table 23–1 , leaving unmentioned fields with default or blank entries. Monitoring Instance Message Data With Oracle BAM 23-55. To configure Source Value Formatting, check the DateTime Specification
checkbox, and select the MMddyy H:mm:ss format in the drop-down list.6. Complete the Source to Data Object Field Mapping so that data from the
incoming XML can be mapped to an appropriate field in the B2B data object. See Table 23–2 for a list of fields in the incoming XML which will be retrieved from the B2B instance table.7. Click Save.
8. Select the B2B_EMS Enterprise Message Source, and click Start. The status changes
to Started in a few seconds. After starting the Enterprise Message Source, any messages that are inserted by the database job into the AQ JMS queue are instantly available in the B2BDO data object. To view the contents of the B2BDO data object, select Data Objects from the Oracle BAM Architect drop-down menu. Browse and select the B2BDO object. Click Contents to view the contents. New rows are inserted into B2BDO as the database job reads incoming messages from the B2B instance table and inserts them onto the AQ JMS queue. For more information on creating Oracle BAM Enterprise Message Sources, see Creating Oracle BAM Enterprise Message Sources in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. Table 23–1 Enterprise Message Source Properties for AQ JMS Queue Property Values and Examples Name Enter a display name for the Enterprise Message Source for example, B2B_EMS. Initial Context Factory Enter weblogic.jndi.WLInitialContextFactory JNDI Service Provider URL Enter t3:localhost:9001 Note: If Oracle BAM is installed is on an Administrator Server use port 9001. If Oracle BAM is installed on a managed server use default port 7001, or the port number configured by the system administrator. TopicQueue Connection Factory Name Enter the name of your connection factory for example, jmsBAMAQQueueCF. TopicQueue Name Enter the name of your JJMS topic or queue for example, jmsBAMAQQueue. Data Object Name: Choose the B2B data object to send the values received from AQ JMS server Operation Choose the Insert or Upsert operation, depending on the use case. Note: The incoming XML value for the date, in the format MMddyy HH24:MI:SS, must be converted into the MMddyy H:mm:ss format that the Enterprise Message Source expects so that it can be stored correctly in the data objectParts
» Oracle Fusion Middleware Online Documentation Library
» Oracle B2B and Business-to-Business E-Commerce Protocols Supported in Oracle B2B
» Payload Obfuscation Security Features of Oracle B2B
» Restricting Access to Document Types
» What You Need to Get Started with Oracle B2B
» Log in to the console. In the Domain Structure pane, shown in
» Accessing Oracle B2B Through Single Sign-On SSO
» Administration Partners Reports Using the Oracle B2B Interface
» Creating a B2B Transaction: An Overview of the Process Flow
» If Oracle JDeveloper is running for the first time, specify the location for the Java
» Create a new SOA composite application, as described in
» On the Name your application page, you can optionally change the name and
» From the Component Palette, select SOA.
» From the Service Components list, drag a component into the designer.
» Click OK. How To Use B2B Binding Components in a SOA Composite Application
» Select Save All from the File main menu.
» Drag B2B to the Exposed Services or the External References swim lane.
» On the Operation page, select Send or Receive, as described in
» On the Document Definition Handling page, select the option on the Basic tab or
» On the Finish page, click Finish.
» Click Finish. How To Use B2B Binding Components in a SOA Composite Application
» If you selected Oracle WebLogic JMS or Oracle Advanced Queuing, then the
» If you selected Send in Step 7, then the Produce Operation Parameters page
» About Using the JMS Integration Type in the B2B Configuration Wizard
» Enabling Debug Mode at Run Time Logging Out: SSO Logout Configuration for Oracle Access Manager
» Introduction to Oracle B2B Document Editor
» Installing Oracle B2B Document Editor Creating Guideline Files: EDIFACT D98 Example
» The Document Hierarchy Introduction to Document Protocols
» Creating Document Definitions Oracle Fusion Middleware Online Documentation Library
» Deleting a Document Definition
» Introduction to Trading Partners Creating Trading Partner Profiles
» Adding Trading Partner Users
» Adding Document Definitions Oracle Fusion Middleware Online Documentation Library
» About MLLP Configuring Channels
» Message Sequencing Configuring Channels
» Using Transport Sync Callback
» Correlating Messages Using JMS Queues
» Configuring Delivery Retry Options
» Using the Auto Create Agreement Feature
» Using Identifiers for Trading Partner Lookup Scheduling Trading Partner Downtime
» Broadcasting Messages to Multiple Trading Partners
» Introduction to Agreements Oracle Fusion Middleware Online Documentation Library
» Creating an Agreement Oracle Fusion Middleware Online Documentation Library
» Deleting and Exporting Agreements
» Importing and Exporting the Design-Time Repository
» Exported ZIP Files Containing Agreement Names in Multibyte Character Languages
» How to Configure the XPath Expression for a Custom XML Document
» Using the EDI EDIFACT Document Protocol
» Using the EDI X12 Document Protocol
» Using the HL7 Document Protocol
» Using the OAG Document Protocol
» Using the Positional Flat File Document Protocol
» PIPs Using the RosettaNet Document Protocol
» Changing Document Definitions After Deploying an Agreement
» Changing Document Definitions After Importing Metadata
» Introduction to Agreement Deployment States
» Click Export. Exporting an Active Agreement
» Creating Custom Identifier Types
» Creating Custom Contact Information Types
» Creating Custom Trading Partner Parameter Types
» Managing Batched Messages Oracle Fusion Middleware Online Documentation Library
» Introduction to Scheduling Trading Partner Downtime Scheduling Trading Partner Downtime
» Deleting Scheduled Downtime Oracle Fusion Middleware Online Documentation Library
» Overlapping Schedules Extending Trading Partner Downtime
» Transport Callouts Introduction to Callouts
» Creating a Callout Oracle Fusion Middleware Online Documentation Library
» Including a Callout in an Agreement
» Implementing a Callout Oracle Fusion Middleware Online Documentation Library
» Purging Design Metadata and Instance Data
» Adding a Listening Channel and Protocol
» Using Transport Protocols Oracle Fusion Middleware Online Documentation Library
» Transport Protocol Parameters Adding Listening Channel Details
» Channel Attributes Exchange Protocol Parameters Security Parameters
» Configuring a Listening Channel Configuring Document Sequencing
» Setting Configuration Parameters Oracle Fusion Middleware Online Documentation Library
» Creating Business Message Reports
» Creating Wire Message Reports
» Creating Application Message Reports
» Creating Error Reports Oracle Fusion Middleware Online Documentation Library
» Creating Conversation Reports Oracle Fusion Middleware Online Documentation Library
» Prerequisites for Running the Command-line Tools
» Archiving Data Oracle Fusion Middleware Online Documentation Library
» Purging Data Oracle Fusion Middleware Online Documentation Library
» Importing Data Oracle Fusion Middleware Online Documentation Library
» Exporting Data Oracle Fusion Middleware Online Documentation Library
» Batching Operations Oracle Fusion Middleware Online Documentation Library
» Deploying Agreements Oracle Fusion Middleware Online Documentation Library
» Creating CPPCPA Properties Templates
» Validating B2B Metadata Verifying Agreement Availability
» Document Protocols selfservice XML files.
» Resubmitting a Message Oracle Fusion Middleware Online Documentation Library
» Scheduling Trading Partner Downtime
» Managing the Keystore Oracle Fusion Middleware Online Documentation Library
» Errors During Import Oracle Fusion Middleware Online Documentation Library
» Introduction to Oracle B2B Web Services
» Using the Outbound Web Service Using the Translation Web Service
» Is Trading Partner Agreement Setup Parameters
» Get Trading Partner Agreement Information Parameters
» Securing Oracle B2B Web Services
» Introduction to Archiving and Restoring B2B Business Messages Archiving B2B Business Messages
» Restoring B2B Business Messages
» AQ Enqueue AQ Enqueue and Dequeue Utilities
» AQ Dequeue AQ Enqueue and Dequeue Utilities
» JMS Enqueue JMS Enqueue and Dequeue Utilities
» Enqueue—Using a JMS JCA Adapter or Custom Utilities JMS Dequeue
» Using the attachmentsDescriptor.xsd
» Click New, and go to the list of JMS resources.
» Select the Foreign Server option, and click Next.
» Enter a Name for the Foreign Server for example, BAMAQForeignServer,
» Enter oracle.jms.AQjmsInitialContextFactory in the JNDI Initial
» Enter datasource=data_source_jndi_location In the JNDI Properties
» Check the Default Targeting Enabled checkbox.
» Select the Connection Factories ta
» Enter QueueConnectionFactory in the Remote JNDI Name field. Click OK.
» Mapping Oracle B2B Instance Messages to Oracle BAM Data Objects
» Creating a Dashboard to Monitor Oracle B2B
» Enabling the Oracle BAM Integration in Oracle B2B
» Programmatically Accessing Instance Message Data
» Declare the Variable_largePayload variable in an outbound BPEL process in the
» In the Assign activity, copy true into the variable.
» Assign the variable to b2b.largePayload in the Invoke activity.
» If you are doing large payload testing, set Show Payload on the Administration
» For an outbound SOA composite, always select the Use file streaming option for
» Create a test JMS module as shown in
» Install Weblogic server and SOA server.
» Navigate to Foreign JNDI Providers under Services on the left-hand navigation
Show more