Creating CPPCPA Properties Templates
19.12 Resubmitting a Message
The following utility resubmits an application message or a wire message for a selected business message. ant -f ant-b2b-util.xml b2bresubmit Table 19–13 lists the options for this utility. Note: The resubmit functionality for payload rectification will only work for Outbound Message for AppMessage only. This is not valid for inbound cases. ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Dmsgid=12345 -Dpayloadpath=scratchviramamofmwhomeAS11gR1SOAbin3a4_req.xml Table 19–13 Options for b2bresubmit utility Option Description Domain Required direction The direction of the message INBOUND OUTBOUND Yes msgsource The message source APPMSG WIREMSG Yes msgid The message ID - Yes doctype Document Type msgstate Message State fromdate The sendTimestamp of the message Date format to be provided within Double Quotes dd-mm-yyyy hh:mm AMPM todate The sendTimestamp of the message agreement Agreement Name B2B Command-Line Tools 19-15 Example 19–25 Resubmits an Outbound Message with Message ID 12345 ant -f ant-b2b-util.xml b2bresubmit -Ddirection=outbound -Dmsgsource=appMsg -Dmsgid=12345\ Other Examples ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Ddoctype=850 ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Dfromdate=29112009 5:40 AM -Dtodate=30112009 7:39 AM ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Dagreement=Acme_GlobalChips_X12_4010_850_File ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=wireMsg -Dmsgstate=MSG_ERROR ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Dfromdate=29112009 5:40 AM -Dtodate=30112009 7:39 AM -Ddirection=OUTBOUND ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Dfromdate=29112009 5:40 AM -Dtodate=30112009 7:39 AM -Ddirection=INBOUND ant -f ant-b2b-util.xml b2bresubmit -Dmsgsource=appMsg -Dmsgid=12345 -Dpayloadpath=tmp850.xml19.13 Scheduling Trading Partner Downtime
The following utility schedules downtime for a Trading Partner. ant -f ant-b2b-util.xml b2bschedule Table 19–14 lists the options for this utility. payloadpath This option is applicable for outbound application message resubmission, by providing the rectified file path. Table 19–14 Options for b2bschedule utility Option Description Domain Required mode Indicates if the script will schedule or unschedule a downtime. schedule or unschedule Yes schedulename A descriptive name for the scheduled downtime - Yes tp Trading Partner Name - Yes except in unschedule mode Table 19–13 Cont. Options for b2bresubmit utility Option Description Domain Required 19-16 Oracle Fusion Middleware Users Guide for Oracle B2B The following are examples of scheduling Trading Partner downtime using the b2bschedule utility. The command does not need to be in a single line. Example 19–26 Schedule Trading Partner downtime for a specific channel and duration ant -f ant-b2b-util.xml b2bschedule -mode=schedule -Dtp=OracleServices -Dfromdate=28052010 06:10 AM -Dtodate=28052010 06:15 AM -Dchannelname=MarketInc_AS2_DC -Dschedulename= Maintenance Example 19–27 Schedule a particular channel for downtime ant -f ant-b2b-util.xml b2bschedule -mode=schedule -Dtp=MarketInc -Dchannelname=MarketInc_ebMS_DC -Dschedulename= Maintenance Example 19–28 Schedule the Trading Partner for downtime In this example, all channels of this Trading Partner will be down for an unknown duration. Executing the unschedule command separately, as shown in Example 19–30 , brings the Trading Partner back to an active state. ant -f ant-b2b-util.xml b2bschedule -mode=schedule -Dtp=MarketInc -Dschedulename= Maintenance Example 19–29 Schedule downtime for a particular duration of time ant -f ant-b2b-util.xml b2bschedule -mode=schedule -Dtp=MarketInc -Dfromdate=28052010 03:05 AM -Dtodate=28052010 03:08 AM -Dschedulename= Maintenance fromate The date and time at which to begin the downtime. Date format to be provided within Double Quotes ddmmyyyy hh:mm AMPM No todate The date and time at which to end the downtime. Date format to be provided within Double Quotes ddmmyyyy hh:mm AMPM No channelname Channel name - No extend Extends a previously created schedule. See Example 19–31 . true No Table 19–14 Cont. Options for b2bschedule utility Option Description Domain RequiredParts
» 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