cancel
Showing results for 
Search instead for 
Did you mean: 

Seeburger Workbench: Message Monitor: ( Inbound ) Initiation to backend pending

Former Member
0 Kudos

Hello Experts,

i have my first inbound X.400 scenario on our plattform. I configured the pi scenario an the x.400 sender communication channel. Now i test the scenario and get the following error in the message monitor from the seeburger workbench.

Status: Initiation to backend pending

Can anyone help me with my error?

Here the Communication Channel Detail:

Task finished with success [7/10/12 12:00 PM]

Processing task [7/10/12 12:00 PM]

Polling started. [7/10/12 12:00 PM]

CC Status: Polling finished, adapter is ready

In the Receiver Determination => Configuration Overview: All Element are visible

I create an entry in the Seeburger Addressbook for P7

and use this ID in the Identifiers of the party  LI009_ABC

agency = ITU Scheme = X.400 Name = X400_abc_test

In the detail for incoming message (Seeburger Workbench: Message Monitor) the right Scenario is used: here LI009_ABC

Kind regards

Tobias Landbeck

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Tobias,

Initiation to backend pending normally occurs when you are trying to send asynchronous MDN to your partner. check with your partner whether he is able to receive sync or async MDN and accordingly confgure your scenario.

Regards

Anandh

Former Member
0 Kudos

Hello Anandh,

thanks for this quick response.

1. Which Status do you mean?

2. The Communication Channel is fine (Status: Polling finished, adapter is ready)

3. Is there any way to deactivate the mdn for test case?

Message ID 0710052623103424

Secondary ID 785196787

Status Initiation to backend pending

Created 07/10/2012 08:31:11

Last modified 07/10/2012 08:31:11

Direction RECEIVED

Subject INVOIC_Daten 129722

Own address {type:X400P7Account}{channel:e8d4ab5085d13848995de6afc23a2364}

Partner address LI009_ABC

Task reference 9a72d7e0-ca69-11e1-a049-4d74c0a84b21

Correlation ID e8d4ab5085d13848995de6afc23a23647129f183ca6911e1b1b500001765d5da

Sending date 07/10/2012 03:26:24

External ID CA21754711E1CA4F170065B6

Message request ID 9a732194-ca69-11e1-c46f-00001765d5da

Logical System 000

Own X.400 address *****

Partner X.400 address *****

Kind regards

Tobias

prateek
Active Contributor
0 Kudos

I want to correct the statement made by Anandh. What he mentions about MDN hold true for AS2 adapter but not exactly for X400. There are notifications in X400 sent using IPMs (Inter Personal Messages).

Do you see the message picked up by the channel and any message in RWB? If not, it may be some incorrect X400 configuration.

Make sure that you created at least 2 X400 sender channels. First will be X400 Polling channel (there should be only 1 such channel in PI). This is configured for your X400 party created for PI. Second will be X400 Virtual Inbound channel specific to your interfaces. This channel will be associated with your external system Party. Create 2 separate sender agreements as well.

I would advise you refer to Seeburger documentation available with Seeburger installation. It provides quite clear configuration steps.

Regards,

Prateek Raj Srivastava

Former Member
0 Kudos

Hello Prateek,

thank for your help. The 2 comm. channels I had already configured, but I had forgot to create the 2nd sender agreement.

I have another questions:

How i join the 2 Comm. Channels?

And where i have to implement the Adressbook ID's

Here my scenario_elements

1. Party: X400_polling

2. CC: Polling_mailbox

3. Party: Suppiler_XY

4. CC: Virt_X400_XY

Kind regards

Tobias

mayank_yadav
Explorer
0 Kudos

Hi Prateek,

What if we are getting  error "Could not deliver as2 message to partner:java.net.ConnectException:Connection timed out#" in case of sending functional acknowledgement to partner? Is it connected to port or firewall issues ?I have checked the Urls & tested with both http & https protocols, but could not find any solution to this.

Regards,

Mayank Yadav

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Tobias,

what is the status? is the adapter ready?

can you provide the screenshot for the better understanding of the error that you are facing?

Regards,

Amar