on 08-14-2007 7:16 AM
In most of my Communication Channel (adpater configuration) in IB Directory,
under the MODULE tab, there is CallSAPAdapter (Local Enterprise Bean),
what does it actually mean,
I tried removinf it from the sender channel, and the scenario was working as well,
but i dont what role it plays in the <b>sender and receiver channel</b>
Information about the CallSAPAdapter can be found in the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/32/43d84072378031e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/30/f0c94055708231e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cd/5af7c0c994e24fb0d0088443513de2/frameset.htm
In the sender direction, this module must be called last in the module chain and it does not use any configuration parameters.
Also You can check following thread.
-Gouri
Award Points if useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey sudheer,
XI has used EJB concept in case of adapter module... in fact CallSAPAdapter is EJB which call the adapter in adapter Engine..
in once the pipeline services are over...Integration Server call the adapter engine.. in adapter engine.. this EJB is called to send the process payload to adapter which send the data to External System...
In case you are developing your own adapter module ( or you can say EJB) then it should be called before CallSAPAdapter EJB... as you ejb will act on the message and once the message is processed completly CallSAPAdapter module is called which send data to extern. system./..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Each adapter needs an adapter module that creates the XI message in sender adapter or creates the outgoing message in receiver adapter.
The CallSAPAdapter is a multi purpose module that can be used in sender or receiver of file and JDBC adapter. Other adapters use different modules.
If there is no entry in the module chain, the adapter framework takes the default module as well, so you do not see any change. If you replace the module by a different module, then the other module has to take over the work of the standard module.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
We use the module porcessor to specify generic module that give Adapter extra functionality.
Some standard module are default provided by sap each of then for diff purpose.
PayloadSwapBean : You can swap the main payload of the XI message with another payload of the message that is an attachment
StrictXml2PlainBean:You can convert an XML document in the main payload of the XI message to text format
XMLAnonymizerBean: You can anonymize XML elements and attributes.
PayloadZipBean:You can compress one or more payloads or extract payloads from a compressed file.
TextCodepageConversionBean:You can swap the code page of the main payload of the XI message and convert the content using the new code page.
DynamicConfigurationBean:You can edit the message header for adapter-specific message attributes.
MessageTransformBean, Migrating Dispatcher Classes
Apart from these you can develop ypur own adapter modules depending on the requirement.
This blog will give you a clear picture.
/people/stefan.grube/blog/2007/02/20/working-with-the-payloadzipbean-module-of-the-xi-adapter-framework
<b>Cheers,
*RAJ*</b>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.