Tuesday Jun 29, 2010

B2B Import : replace flag

[Read More]

Friday Jun 25, 2010

Side by Side versioning in Oracle B2B

[Read More]

Tuesday Jun 08, 2010

How Archive work in Oracle B2B 11g.

[Read More]

Friday May 28, 2010

Integrating OSB - B2B for a healthcare scenario

[Read More]

Thursday May 27, 2010

AS11 Oracle B2B Sync Support - Series 2

[Read More]

B2B - OSB Action Series

[Read More]

Thursday May 20, 2010

Commandline Purge in AS11

AS11 - B2B offering consists of numerous features that have been made available via commandline approach. Most of these are supplement to the already available User Interface based approach. One such is purging of runtime data.

The commandline purge option enables the users to purge the runtime data, based on various criteria. This is an ANT based command, provides the flexibility to selectively set the criteria to purge the runtime data.

Providing the command line option also enables the administrator to purge in bulk, without visiting the B2B UI, which can also be used for automation purpose

By default archival is turned on for purge activity. As a pre-requisite, the respective folder needs to be configured in database with the proper permission. When no filename is provided for archived data, the sysdate will be considered for filename.

Below are the various options to purge the runtime data


Option

ANT option

 

Message state

-Dmsgstate

 

Date range

-Dfromdate,  -Dtodate

Format : dd/mm/yyyy hh:mm AM/PM

Trading partner

-Dtp

 

Direction

-Ddirection

 

Message Type

-Dmsgtype

 

Agreement Name

-Dagreement

 

IdType/ value

-Didtype,  -Didvalue

 

Archive

-Darchive

True/false

By default true

Archive file name

-Darchivename

File name (optional), will be used when archive is set to true.


Note: When using -Darchivename the value must be a unique file name. An existing file name used with -Darchivename throws an exception


Below are the few of ant commands and various options.

 

Purge based on date range and message state:


ant -f ant-b2b-util.xml b2bpurge -Dmode=RT -Dfromdate="19/12/2009 1:04 AM" -Dtodate="19/12/2009 1:05 AM" -Dmsgstate=MSG_COMPLETE -Darchivename="filename.dmp"

 


Purge based on direction:

ant -f ant-b2b-util.xml b2bpurge -Dmode=RT -Ddirection="OUTBOUND"



Purge based on agreement Name:

ant -f ant-b2b-util.xml b2bpurge -Dmode=RT -Dagreement="agreement_name"


Purge based on Trading partner Name:


ant -f ant-b2b-util.xml b2bpurge -Dmode=RT -Dtp=GlobalChips


Purge based on Message State:


ant -f ant-b2b-util.xml b2bpurge -Dmode=RT -Dmsgstate="MSG_COMPLETE"



ant -f ant-b2b-util.xml b2bpurge -Dmode=RT -Ddirection="OUTBOUND" -Dmsgstate="MSG_COMPLETE"




[Read More]

Thursday Mar 25, 2010

Oracle B2B 11g - Transport Layer Acknowledgement

[Read More]

Monday Feb 22, 2010

What do I like Most in 11g - Oracle B2B 11g Metrics

[Read More]

Wednesday Feb 10, 2010

Oracle B2B Load Balncing using BIGIP

[Read More]

Tuesday Jan 19, 2010

Acknowledgement Management in 11g

[Read More]
About

To Discover and discuss the capability of B2B in the world of Trading Partner Integration. This blog is primarily intended to share thoughts on Oracle B2B Product and to share best practices in performance, scalability and various topologies.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today