cancel
Showing results for 
Search instead for 
Did you mean: 

BPM-Queries

Former Member
0 Kudos

Hi,

I'm working with BPM Scenario can i get some Detailed Description on the Configuration Part used in general.

My Scenario is just to transfer a file->XI->file.

Regards,

Prashanth

Accepted Solutions (1)

Accepted Solutions (1)

former_member187339
Active Contributor
0 Kudos

Hi Prashant,

1) Create a service for file (eg. File Service)

2) Make two communication channels inside that, one as Sender (sends file to XI) and another as Receiver (sends file from XI).

3) Now Create Business Process (eg BP). Just follow the wizard.

4) Create Sender Agreement, between File Service and BP

5) Create two Receiver Determination.

(a) One between File Sevice (Sender Interface) and BP

(b) Another between BP and File service (receiver Interface).

6) Create the corresponding two Interface Determination.

7) Create a receiver Agreement using the receiver communication channel

Hope this will be helpful.

Regards

Suraj

Former Member
0 Kudos

Hi Suraj,

Thanks for your reply.If I have to Create two Interface Determination then i should have created two Interface Mapping?

is this the process happening while using BPM?

Sender->XI(Integration Process)->Receiver.

So i need two receiver

1. Sender->XI(Int Process).

2. XI(Int Process)->Receiver.

If I'm wrong please correct me.

Thanks in advance,

Prashanth

former_member187339
Active Contributor
0 Kudos

Hi Prashanth,

<i>>>If I have to Create two Interface Determination then i should have created two Interface Mapping?

</i>

No you just create a single Interface Mapping

IM should be between the Outbound Message Interface and the Inbound Message Interface. MM Should be between the Input MT and Output MT.

<i>

>> is this the process happening while using BPM?

Sender->XI(Integration Process)->Receiver.</i>

Yes this is the process happening..

Your BPM should consisits of the following steps :

1) Receive Step

Mode = asynchronous

Message = container variable of outbound Interface say FILEIN

2) Transformation Step

Interface Mapping = As created above

Source Message = FILEIN

Target Message = FILEOUT

3) Send Step

Mode = asynchronous

Message = container variable of inbound Interface say FILEOUT

Hope this will be helpful.

Regards

Suraj

Former Member
0 Kudos

Hi,

You need two interface determns: one for file to bpm and other for bpm to file.

Only one interface mapping which is specified inside the bpm in the transformation step.

<i>> So i need two receiver

>1. Sender->XI(Int Process).

>2. XI(Int Process)->Receiver</i>.

No.....theres only one receiver: ie file(bpm to file)

regards

priyanka

Former Member
0 Kudos

Hi Suraj,

Thanks for your reply.While creating transformation I'm always getting Message Interface Abstract type and not the Inbound or the outbound Msg Interface,and I'm Little confused with Configuration.

1.What is a Bussiness Service?

2.In my Receiver Determination Which will be my Sender service and Receiver service(Is it the Source sender or the Integration Process)?

3.How many Interface determination do i need?

Regards,

Prashanth

former_member187339
Active Contributor
0 Kudos

Hi Prashanth,

<i>>>What is a Bussiness Service?</i>

A business service represents an abstract unit for addressing the senders and receivers of messages. You can use a business service to group interfaces.

go thru this link

http://help.sap.com/saphelp_nw04/helpdata/en/fe/131eb4ef2fb344abf471c9eac0063a/frameset.htm

<i>

>>In my Receiver Determination Which will be my Sender service and Receiver service(Is it the Source sender or the Integration Process)?</i>

(1)

Sender = File Service

Receiver = Integration Process

(2)

Sender = Integration Process

Receiver = File Service

In Receiver Agreement

Sender = Integration Process

Receiver = File Service

<i>>> 3.How many Interface determination do i need?</i>

Two, one for each Receiver Determination.

Along with these I hope you have created the following interfaces in your design part :

1) Input file Message interface (2 nos)

(a) One Outbound, Asynchronous.

(b) One Abstract, Asynchronous.

2) Output file Message interface (2 nos)

(a) One Inbound, Asynchronous.

(b) One Abstract, Asynchronous.

You use these Abstract Interfaces in your BPM when you create container variables.

Hope this will be helpful.

Regards

Suraj

Former Member
0 Kudos

Hi,

In the interface determination you need to mention ur abstract interfaces and not the outbound and inbound interfaces.

1 its under the buisness service tht you specify ur adapters.

2 REcvr determination1:

sender service: fileservice name

recvr service: bpmname

Recvr determination2 :

sender service: bpmname

recvr service: fileservice name

3) two interface determinations

ONE :

sender service: fileservice name

sender interface : outbound interfacename

recvr service: bpmname

configure inbound interface: abstact file interface

TWO:

sender service: bpmname

sender interface : abstract file interface recvr service: fileservice name

configure inbound interface: inbound file interface

Regards

priyanka

Former Member
0 Kudos

Hi Suraj,

When use Abstract Message Interface in BPM I'm not able to activate it since its asking for the Source Msg and Target Msg in BPM as Outbound and Inbound Interface.

Regards,

Prashanth

Former Member
0 Kudos

Hi,

In interface mapping,when you mention ur abstract interfaces...click on read interfaces button...u get the message tytpes below and specify ur message mapping there.Save and activate.

hope you have constructed two container variables in ur bpm which are abstract.Use them in the transformation step n the process.

Regards

Priyanka

Message was edited by: Priyanka Balagangadharan

former_member187339
Active Contributor
0 Kudos

Hi Prashanth,

Just check whether you are using your Abstract Interfaces for doing the Interface Mapping.

Source Interface = Abstract Interface for Input File.

Target Interface = Abstract Interface for Output File.

Hope this will be helpful.

Regards

Suraj

Answers (1)

Answers (1)

Former Member
0 Kudos