Archiving Message PI with Seeburger AS2

Hello Experts,
we have an AS2 Scenario with incoming Invoic. Now my question: It is possible to archive our incomming messages after the as2 adapter has decrypt the message an before the message is processed in the pi. Where can i configure the archive step?
here is what i found in SDN:
The new B2B Add-On for SAP NetWeaver Process Integration:
Archiving of B2B messages: Adapter module extending basic archiving functionality which is built into the AS2, X.400 and OFTP adapter. In and outgoing messages can be stored on the file system with more information (e.g. IDoc number in filename, archiving per business partner, etc.).
Kind regards
Tobias

@Venkat - "AS2 adapter doesn't support the archive functionality by default."
I disagree. There is a FileStore module provided by Seeburger which provide extensive Archiving capabilities. If you have the license, there is an Archiving guide available with it which explains the process.
A simpler and effective way is of course to use createFiles option with BIC module if you have that license.
Regards,
Prateek Raj Srivastava

Similar Messages

Client Auth and SSL with Seeburger AS2 adapter

Hello All,
We are using the Seeburger AS2 adapter in our landscape and I am in the process of setting the same up and have made quite some progress in all my issues.
and I hope that you will be able to help me out.
1. Server SSL on Receiver AS2 adapter
I am sending a message from XI using the Receiver AS2 adapter to my AS2 test tool using Server SSL.
This is working perfectly fine. In my AS2 adapter I have selected HTTPS as the protocol and the message goes via SSL to the target test tool, is processed and the MDN comes back to XI perfectly.
The issue here is :
Irrespective of what is provided in the Server Certificate ( Keystore) , the message goes to my target test tool. I even left this field blank with no certificate entry and still the SSL connection was established and the message went to the target system.
Is there no validation that XI does here? I am lost what is the use of this entry Server Certificate if XI blindly accepts all SSL connections.
I am using a Decentral Adapter Engine with LoadBalancer.
2. Client Auth on Receiver AS2 Adapter
I tried to perform Client Authentication by proving my Server's private key in the AS2 adapter. The corresponding public key is loaded in my partner's Keystore.
XI error's with the error "SSL handshake failed - Bad Certificate" .
I am not sure why XI is erroring out here and I have a feeling that I have misunderstood the use of the fields in the AS2 adapter,
Server Certificate ( Keystore) and Private Key for Client Authentication.
Has anyone tried this? If further details are needed, I will be able to furnish the same.
Regards,
Bhavesh

Hello Jens,
Thanks for your reply.
1. The Encryption and Signature part of the Interface is working absolutely fine and I use the same concept highlighted by you - The Sender always signs the message with his private key and encrypts with message with the partner's public key in the corresponding agreement.
2. Server SSL is also working perfectly fine, i.e, when XI initiates the connection the SSL connection is established to the partner.
3. Mutual Auth was the issue where I was getting the bad certificate issue.
To investigate further I moved the same setup to my Central Adapter Engine and all the issues I had described above seem to have vanished and things work exactly as I was expecting, ie.
The field : Server Certificate (Keystore) is used to provide the Target System's Server SSL's public Certificate.
The field : Private Key for Client Authentication is used where XI provides its own Server SSL's private key for Mutual / Client Authentication.
The problem seems to be with my Decentral Adapter engine and not my central adapter engine and so I guess,
1. I either have the incorrect certificates on my Decentral Adapter Engine.
2. I also have 2 instances of a Decentral Adapter Engine with a Webdispatcher and so maybe the 2 Visual Admin's of the 2 Decentral AE are inconsistent.
3. Maybe it was just a long day and I did something wrong
Will investigate further for the root cause but I am glad that my concepts remain intact and things do work as I expected them to work.
A blog on all this is on the cards sometime soon.
Cheers,
Bhavesh

Content based receiver determination with Seeburger AS2 adapter

We are planning to use the Seeburger AS2 adapter on our XI 3.0 installation to post custom XML documents to XI from external business partners. The problem we have is to do the receiver and interface determination based on the xml message type that is submitted. How can we identify what is the name of the root xml node (which is representing the message type that was submitted to us) during the receiver determination and specify conditions for the receiver determination based on this? We can not use the Seeburger Classifier module here as this is only determining the mapping name to be used for an EDI conversion but can not handle any type of XML message.

Rudy,
I think the easiest way would still be the ReceiverDetermination and creating an XSD that contains the main important TAGs from the different messages.
That should allow you to test for the existing of certain important TAGs or check the value of some TAGS.
I don´t know about aedaptive-adapters, but I don´t think that they are Drummond-Certified. Check out...
http://www.drummondgroup.com/html-v2/as2-companies.html
Without this certification, a lot of your partners might not allow you to use this adapter if you wanna make AS2 with them.
Greetings
Stefan

Issues with Seeburger AS2 alerts

Hello All,
I am trying to setup an alert rule for any failures in the AS2 adapters.
I have created an alert rule in the RWB, with the adapter type as AS2.I have created the alert category as well.
When the AS2 message is unable to reach the destination system, the communication channel errors out with the description about the connection issue. But for some reasons, the alert rule is not called. I could see in the "SXMSALERT_LOGREADER" report that No active rule for this Adapter Framework exception. I have selected a * for all the filter criteria in the alert rule except for the adapter type (which is filtered as AS2).
Are my basis guys missing any alert enablement functionality while deploying the AS2?
Pls note that I am able to receive email alerts if the adapter type is selected as File or JMS instead of AS2.
Pls help me.
Edited by: Senthilnathan Natarajan on Oct 4, 2011 5:53 PM

I'm resending this since I did not have any luck with it the first time.
We also have an oss note waiting to be responded on this subject.
When I send messages using Seebuger FTP adapter, I see the following information in the SAP message monitor -
"Message entered module processor exit bean and will be transferred to JCA adapter".
But does not get to IBM VAN mailbox. How do I trace from this point onwards.
Should I use Seeburger monitoring tool for this? If so, I don't see anything in Seeburger monitoring (used all criteria).
Please let me know if you have any information on this subject.
Thanks,
Parimala

Seeburger AS2 - message does not arrive when "Athentication required" is ON

Hi guys!
If somebody of you is using the Seeburger Adapter:
I have an inbound scenario and everything works fine. But when I set "Authentication Required" flag to be ON, messages are refused. This is strange, because incoming messages are signed.
Any ideas, what could be wrong? There are several settings for certificates and maybe I have some wrong setting.. Does anybody have experience with this?
Thank you, Peter

Sai, you probably don't have experience with Seeburger AS2, do you? It works in a special way - that's why I'm asking people, who have experience with this..
But for clarification: My inbound Seeburger AS2 channel receives message scorrectly, but when I enable uthentication on it, AS2 messages are refused - so they are not in the AE, they are not in the IE.
Peter
p.s. I will not reward your answer, sorry
Message was edited by:
Peter Jarunek

Seeburger AS2 Sender : EOIO

Hi All,
Is it possible to achieve EOIO with Seeburger AS2 sender channel? I am not seeing any parameter for configuring the same (though it has EOIO mode for split mapping).
The idea is to send all the messages received for a particular interface to be routed to a EOIO queue. Is this possible with AS2 sender channel?
Regards
Suraj

Hi Prateek,
>>SAP_AS2Adapter_en.pdf - Page 6 (in my version).
I have checked seeburger manuals and found page six to be something different (may be different version document). From the document I found a particular section
The following Qualities of Services are supported:
u2022 Outbound (AS2 sends a message to an external partner)
Best Effort
Exactly Once
Exactly Once in Order
u2022 Inbound (AS2 adapter receives a message from external partner)
Exactly Once
This was in Section 2.5 under Overview. May be if you tell me the section I would try to read through it,
I have tried your suggestion
namespace: http://seeburger.com/xi/AS2
parameter name "QoS" value "EOIO" and
for name "QueueName" value "<your actual queue name>"
but it didn't help. If I use with "write", there was no entry in MONI, and if I use it with "insert" the entries were created but it didn't go to the EOIO queue (as the SAP:QualityOfService is still ExactlyOnce in SoapHeader->ReliableMessaging)
<SAP:Record namespace="http://seeburger.com/xi/AS2" name="QoS">EOIO</SAP:Record>
<SAP:Record namespace="http://seeburger.com/xi/AS2" name="QueueName">INT014</SAP:Record>
Anyway thanks for your inputs
Regards
Suraj

There is no key entry with such alias in keystore seeburger AS2

Hi,
Error message in RWB shows the following
Message entered module processor exit bean and will be transferred to JCA adapter
2011-04-06 06:19:29 Success SEEBURGER/AS2: Received order from system.
2011-04-06 06:19:29 Error Unable to forward message to JCA adapter. Reason: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiExc
2011-04-06 06:19:29 Error Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.
2011-04-06 06:19:29 Error The message status set to NDLV.
2011-04-06 06:19:29 Error MP: Exception caught with cause javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: There is no key entry with such alias in keystore, SEEBURGER AS2: AS2 Adapter failure # java.lang.Exception: AS2 message composition failed: com.seeburger.ksm.cryptoapi.exception.CryptoApiException: java.security.PrivilegedActionException: com.seeburger.ks
unable to send / receiver messages through AS2. Please let us know what could be the error. How/ where to resolve it.

Please check the SDN thread below
AS2 Adapter Configuration to Customer / no signature certificate
Also, check the help page below
http://help.sap.com/saphelp_sm40/helpdata/DE/84/be18d66b2a47f6b4adc704a7c0e23e/content.htm
for instructions on how to get the "SEEBURGER EDIINT AS2 Adapter for SAP Exchange Infrastructure Configuration Guide" from the Service Marketplace. Then, on this guide, please check the configuration according to your sender or receiver communication channel regarding the Security (certificates) parameters.
Are the key Store entries imported correctly? Please check if the certificates were imported in the right order and none of the certificates on the chain are expired.

Seeburger AS2 Adapter sending message error

I have configured a FAck scenario as described by the Seeburger Manual and am testing a AS2 messaging scenario with a vendor (basically the inbound EDI message is passed to the Seeburger splitter to create a new message for the inbound order, and then the existing payload is mapped to a Funcational Acknowledgement and sent back to the vendor). I receive the message fine and the message split to create the order works fine, however when the FAck is passed to the AS2 receiver adapter (for transmission to the 3rd party) I get the following error:
LOCATION [null, null, 91fcf4f0-5223-11dd-9c8d-5cd90a641602] >> ERROR TYPE [, COMPONENT_ERROR, not retryable, not fatal]] >> DESCRIPTION [AS2 Adapter failure >> MID
MID <[email protected]22.2> already exists. - Duplicate will not be sent [LOC: com.seeburger.as2.component.AS2Client.storeMID]
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
If I extract the same inbound message from the payload and pass it in using a file adapter (rather than the AS2 sender adapter) then the functional acknowledgement is created and transmitted to the vendor without any issues ...
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Regards,
Jason

Hello ,
same issue occurred in my system
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Please advise asap.

Seeburger AS2 Adapter: Receiving multiple messages

Hi guys,
I'm having some trouble using AS2 Adapter for receiving multiple messages. The problem is really similar to Peter's problem.
Seebuger AS2 adapter for XI as sender for multiple messages
I have it configured for one scenario and it's working fine. The problem is when I'm trying to receive other messages for the same Party but different services. Meaning, I've one Party(example BMW) and several services (BMW_DE, BMW_USA, etc). I'm able to receive messages from service BMW_DE but when configuring BMW_USA I'm getting HTTP 403 Forbidden.
This error may have different reasons:
a) You or your partner has entered an incorrect AS2 ID for one of the involved parties.
b) A valid sender agreement is missing.
c) There are more then one AS2 sender agreements with the same sender AND receiver party.
d) The corresponding inbound channel is set to inactive.
And the problem is that there are two sender agreements. Although the services are different, XI is not able to find the correct sender agreement to be used. After deleting the second second agreement, I'm able to send the respective message....
Can anyone give me a hint on how to solve this problem?

Hi,
this is done by different AS2 subjects. The sender agreement is selected based on this. So create separate AS2 receiver adapters for every message you need and put there different message subjects.
So if you'll have 3 AS2 receiver channels with subjects:
MessageType1_DE
MessageType1_US
the AS2 adapter will work like following:
first it tries to find an exact message subject, if it is found, message is "assigned" to this sender agreement. If no exact message matches the subject, then wildcards are used. (this mechanism is described in the Seeburger AS2 guide).
If you are getting 403 HTTP code, there may be also problem with authentication certificates.
Another problem may be, you don't have configured AS2 receiver channel for current subject.
Does this help you? Or you meant it another way?
Peter
p.s. check the answer above my post, Vardharajan's right
Edited by: Peter Jarunek on May 19, 2008 2:11 PM

Error while parsing AS2 message: DECRYPTION_ERROR in Seeburger Workbench

Dear all,
In our production SAP PI 7.1 server, we are getting the below error in the Seeburger Workbench screen.
Error:
State Error on receive, task will not be retried
"State Description Error while parsing AS2 message: DECRYPTION_ERROR # com.seeburger.ediint.edi.EDIMessageException: message decryption failed: failed to decrypt message: provider BC not found"
Imp points to note are:-
1. This error is not specific to one interface. 3-4 interface messages have this error.
2. And even for a particular interface that has this error, we could see that some messages are getting processed without any issues, and some error out, so we are not in a position to conclude anything.
Because of the above issue, many business critical messages are pending to be processed.
If any one has encountered this before error, pls share your inputs to resolve this or any workarounds to temporarily handle the issue will be appreciated.
Thanks,
Younus

Hello Younus,
We are facing exactly same problem in some of our scenarios.
It is strange that this error doesn't occur all the time ,only some messages fail with this error.
I know ,this is a worst approach,but as we couldn't find any solution,we have adopted a workaround to request partner to resend the message and this works well .
Thanks.
Regards,
Shweta

Seeburger AS2 -Message Dumping

Hi All,
We are able to receive and send message from and to third party mail box successfully. But when we enable message dumping for debugging via J2EE Admin for AS2 Adapter we are not able to receive message from the third party mail box.
As per SEEBURGER EDIINT AS2 Adapter for SAP Exchange Infrastructure 3.0 document it is given as follows
"For debugging purposes, it is possible to dump the complete AS2 message or MDN to a directory on the SAP XI Server. The outbound and incoming AS2 messages are stored with complete HTTP headers. This also applies to the outbound and incoming MDNs."
So can anyone provide help to solve the issue.
Regards,
Prakash

Hi Prateek,
If message dumping is enabled then message is not reaching to the AS2 server and third party mail box receiving some error as not able to send message to the partner.
If meesage dumping is disabled then the message is reaching to the AS2 server successfully.
As we need to communicate with two mail box .So message exchange with one mail box is successfull and when second mail box pushes data to our As2 server it is not reaching and the partner is telling that negative MDN is received.
But when we check in the seeburger monitoring message from the second mail box is not shown, as i know that negative MDN is sent in cases like decryption is failed.
For debugging the above case message dumping is enabled and checked with the first mail box but it is also failing as I explained previously.
Seeburger Version is 1.7.1
So can you provide some solution to solve the issue with message dumping.
Regards,
Prakash

Outbound AS2 with Seeburger Adapter

I am attempting to send a flat file using Seeburger's AS2 adapter.
1. I created a new scenario.
2. In the identifier section of the partner, I added a line for Seeburger | AS2ID | theID.
3. I created a communication channel of type AS2. It's setup for Transport Protocol HTTP. I gave a server ip address, port, url, timeout, and no MDN.
4. The Receiver Agreement contains the signing key, encryption certificate, and authentication certificate.
In my scenario, I have a sender agreement and communication channel that is monitoring a directory for the file to be sent. Then the document is supposed to be sent to our partner. When I attempt a transmission, I get the following error when I look at communication channel monitoring.
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing..
Sending failed. [2/19/09 6:14 PM]
Error type: COMPONENT_ERROR,NOT_TRANSMITTED >> Error date: 2/19/09 6:14 PM >> Description: AS2 Adapter failure Outbound configuration error: Sender configuration incomplete - perhaps AS2ID missing.. com.seeburger.as2.AS2Plugin.execute(AS2Plugin.java:321) [2/19/09 6:14 PM]
AS2 Adapter failure [2/19/09 6:14 PM]
I am not sure where my problem exists, and hope someone can assist me. I don't quite understand the error because I have the AS2ID entered in the Party (where I am sending to).
Larry

Hi
Check this link, this may help fixing your problem
Re: SEEBURGER AS2: 403 Forbidden #
also
Re: Seeburger AS2 comm channel problem (B2B) - "perhaps AS2ID missing"
Regards
Vishnu

Standard Adapter Module "Message Transform Bean" in Seeburger AS2 Adapter

Hi,
    I am calling standard adapter module "Message Transform Bean" in seeburger AS2 Sender adapter where I am getting the following error :
ClassNotFoundException:com.sap.aii.messaging.adapter.Conversion . Can anybody help me on this. Appreciate for your respoinse.
Thank you,
Mallikarjuna Rao M

Hi,
Thank you for your replies I manage to get NWA dump for this issue.. Here is the log
Could not call backend system: Error in ???-module:Transform: failed to set up the transformer for channel 6857fd15f84d3e23a7b0f51ca1851b20; modkey TXT2XML; caused by java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
[LOC: com.seeburger.as2.impl.SHCInitiatorProcessor.initiateToBackend] Caused by: Error in ???-module:Transform: failed to set up the transformer for channel 6857fd15f84d3e23a7b0f51ca1851b20; modkey TXT2XML; caused by java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
at com.seeburger.xi.api.module.impl.nw71.SeeModuleProcessorLocal71.process(SeeModuleProcessorLocal71.java:55)
at com.seeburger.xi.connector.fw.InitiationThread.run(InitiationThread.java:101)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassNotFoundException: com.sap.aii.messaging.adapter.Conversion
Loader Info -
ClassLoader name: [sap.com/com.sap.aii.af.mod.trans.app]
Living status: alive
Direct parent loaders:
   [system:Frame]
   [service:servlet_jsp]
   [service:ejb]
   [library:engine.j2ee14.facade]
   [library:com.sap.base.technology.facade]
   [library:com.sap.aii.af.lib]
   [library:com.sap.aii.af.sdk.lib]
   [service:com.sap.aii.af.cpa.svc]
   [service:com.sap.aii.af.svc]
   [service:com.sap.aii.adapter.xi.svc]
   [library:com.sap.aii.adapter.lib]
Resources:
   D:\usr\sap\BWD\DVEBMGS00\j2ee\cluster\apps\sap.com\com.sap.aii.af.mod.trans.app\EJBContainer\applicationjars\com.sap.aii.af.mod.trans.ejb.jar
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:259)
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:228)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:353)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at com.sap.aii.af.modules.trans.MessageTransformBean.loadClass(MessageTransformBean.java:121)
at com.sap.aii.af.modules.trans.MessageTransformBean.setup(MessageTransformBean.java:178)
at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:346)
at sun.reflect.GeneratedMethodAccessor484_10002.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy2674_10002.process(Unknown Source)
at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:249)
at sun.reflect.GeneratedMethodAccessor311_10002.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy102_10002.process(Unknown Source)
at com.seeburger.xi.api.module.impl.nw71.SeeModuleProcessorLocal71.process(SeeModuleProcessorLocal71.java:43)
Waiting for your valuable inputs on this.
Thank you,
Mallikarjuna Rao M

Archiving SMS messages offline with PC Suite 6.7

First of all, I'm not a computer expert so I really hope someone can help me! I downloaded PC Suite 6.7 and would like to archive my sms messages (received messages and sent messages) offline on my PC. But it seems that I can only see my messages when my phone is connected to the PC, once I disconnect, the messages are no longer available. This means that I cannot archive my messages. I used to have an old version of Nokia Phone Editor 4.5 with my old cellular which allowed me to do this.
Basically, what I want to do is this:
- Archive my messages on a regular basis so that I can delete them from my phone and free up its memory
- Access these messages even when my phone is not attached to the PC
It seems that I cannot view my Contacts either unless my phone is connected. Why is this? I did not have this problem with Phone Editor 4.5. Should I install an older version of PC Suite?
I am running Windows XP and using a cable connection.
PLEASE HELP ME!!!! I'M GOING CRAZY!!!
Thanks, Michelle

Hi, I don't have a solution either. I have tried copying the files while the phone is connected into a separate folder. The files will copy and they are accesible, but the dates are all messed up. Rather than the date the message was sent, it notes the date the file was created which is the date I copied them. So, messages sent over the course of a week all have the same date and almost the same time.
I have also tried the export message option which makes each message a single cell readable in Excel but that single cell includes everything, the message, date, time, sender...certainly not a convenient way to archive messages.
One main reason I decided to invest in a more expensive Nokia was the belief that there would be a good solution for archiving messages. I am sadly disappointed.

Seeburger AS2 message signatures

Hi,
I have deployed the Seeburger AS2 adapter and it seems to work fin.
I would like to get a hold on the original signed messages both outgoing and ingoing direction. I have configured the dump parameter for seeburger, which gives 5-6 messages pr message send. The problem is I cannot find any of the IDs in XI, since XI uses a new GUID for the messages.
Have anybody found a way to store the Signatures in a meaningful way, which can be used in a dispute.
/regards
Daniel Graversen

I have not found a solution

Archiving Message PI with Seeburger AS2

Similar Messages

Maybe you are looking for