Validating B2B Metadata Verifying Agreement Availability

19-14 Oracle Fusion Middleware Users Guide for Oracle B2B ebMS Samples The ebMS samples are located in: samples selfservicecustom b2b-106-Custom_1.0_orders_ebMSbuyer_setup_selfservice ebms_buyer_ss.xml The schemas are located in: samples selfservicecustom b2b-106-Custom_1.0_orders_ebMSbuyer_setup_selfserviceschemas Use the following command: ant -f ant-b2b-util.xml b2bselfservice -Dinput=samplesselfservicecustom b2b-106-Custom_1.0_orders_ebMSbuyer_setup_selfservice ebms_buyer_ss.xml

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.xml

19.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 Required B2B Command-Line Tools 19-17 Example 19–30 Un-scheduling the scheduled event ant -f ant-b2b-util.xml b2bschedule -Dmode=unschedule -Dschedulename=Maintenance Example 19–31 Extend an existing schedule Create a schedule for a particular time frame for all the channels for a remote tp by entering the following: ant -f ant-b2b-util.xml b2bschedule -Dtp=GlobalChips-Dfromdate=31082010 10:47 AM -Dtodate=31082010 10:57 AM -Dschedulename=Load -Dchannelname=GlobalChips_File_Endpoint Extend the schedule by creating another schedule with the same name, with the start time as the end time of the previously created schedule 31082010 10:57 AM, and the end time to which you want to extend the schedule to, and then pass the parameter -Dextend=true: ant -f ant-b2b-util.xml b2bschedule -Dtp=GlobalChips-Dfromdate=31082010 10:57 AM -Dtodate=31082010 11:57 AM -Dschedulename=Load -Dchannelname=GlobalChips_File_Endpoint -Dextend=true

19.14 Managing the Keystore

Certificate expiry must be identified and notified to the Administrator as it affects the message flow with security. Oracle B2B exposes Public APIAnt commands to check the certificate for expiry. You can use b2bmanagekeystore to define a schedule and encapsulate these APIs for proper alert mechanism. ant -f f ant-b2b-util.xml b2bmanagekeystore [-Dmode=list | -Dalias=cert_name | -Ddays=num_of_days] Example 19–32 Get a list of certificate aliases ant -f ant-b2b-util.xml b2bmanagekeystore -Dmode=list Example 19–33 Get the status of a certificate ant -f ant-b2b-util.xml b2bmanagekeystore -Dalias=MarketInc_Cert Note: As a pre-requisite, it is required to configure the Java key store in Oracle B2B. Table 19–15 Options for b2bmanagekeystore utility Option Description Domain Required mode List all the certificate alias in the keystore and its expiry dates list No alias Certificate status and its expiry date of the provided alias No days List all the certificates which will expire within the days specified integer No