PCK in XI

Hi,
PCK in XI
Thanks,
RamuV

Hi Ramu,
Purpose
The Partner Connectivity Kit (PCK) enables you to connect to SAP Exchange Infrastructure (SAP XI).
The PCK is a J2EE-based application that uses the Adapter Framework, which is also based on the SAP XI Adapter Engine. The adapter framework is based on the SAP J2EE Engine (part of the SAP Web Application Server) and the J2EE Connector Architecture (JCA).
Implementation Considerations
The Partner Connectivity Kit is based on the SAP Web Application Server 6.40 J2EE server.
Features
●      Using the PCK, you can configure how messages are exchanged between senders and receivers by defining collaboration profiles (communication parties, services, and communication channels).
●      The PCK enables you to convert information to the SAP XI messaging protocol. This conversion is made possible using adapters.
Conversely, you can convert the data that you receive from the Integration Server to other formats so that it can be used by your applications. When defining the flow of messages that are processed by the PCK, one of the end points is always the Integration Server.
●      The SAP Conversion Agent by Informatica allows you to convert unstructured, semi-structured, and structured data in XML format using an adapter module. See: Conversion Agent
●      A graphical mapping editor enables mapping between source and target structures. If you have implemented XSLT or Java mappings and packed them in a JAR or Zip file, you can import these archives.
●      Monitoring is available to enable you to monitor and track messages that flow through the PCK, and to monitor the adapters.
●      Information on adapter development is available for partners. This also contains information on how to create a module to extend the adapter functions. See: Adapter and Module Development
●      The configuration example shows you which objects must be created in the PCK and in the Integration Server of the XI customer to configure a message exchange.
refer the below link for more informatrion:
http://help.sap.com/saphelp_nw04/helpdata/en/17/a73d40c6d98437e10000000a155106/frameset.htm
/people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-1
/people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-2
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4256 [original link is broken] [original link is broken] [original link is broken]
chirag

Similar Messages

How to use digital certificate for client authentication in PCK

My sap jca adapter need support digital certificate on client authentication. how to implement it in j2ee or pck?
Message was edited by: Spring Tang

refer the following links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/092dddc6-0701-0010-268e-fd61f2035fdd
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b2a56861-0601-0010-bba1-e37eb5d8d4a9
please let me know if u dont find relevant information

FileSys with PCK Vs R/3 with XI

Hi Experts,
I'm a learner in XI. I have some doubts about PCK.
In the scenario "FileSys with PCK --> R/3 with XI", for posting PO from FileSys to R/3,
- the PCK receive the source XML msg through File Adapter and it will send the msg to XI Box through XI adapter.
- the XI will receive the msg through XI adapter and post into R/3 through IDOC adapter.
a) Interface mapping will not be there in PCK. If I am right, what transformation takes place for the source XML msg after the PCK receives it.
b) What exactly the XI adapter do in this scenario.
Please clarify me.
Thank you.

a) Interface mapping will not be there in PCK. If I am right, what transformation takes place for the source XML msg after the PCK receives it.
>> iam not usre y again using tranforamtion here.
b) What exactly the XI adapter do in this scenario.
>> you interact from XI to PCK using XI adpter this is option for perfomance.

Is it possible to test XI Adapter on PCK by JNDI lookup?

Hi, friends
I can't test the XI Adapter by using the communication channels and sender/receiver agreements on a standalone PCK (without XI server to be connected). Is it possible to test XI Adapter on PCK by JNDI lookup?
I can locate the XI Adapter by JNDI lookup (JNDI name is configured on SampleRA.xml):
ConnectionFactory cxf = (ConnectionFactory)initctx.lookup("deployedAdapters/sample_ra/shareable/sample_ra");
But later it failed to get the ConnectionSpec and create the Connection. Could anyone give me a sample code for testing XI Adapter by JNDI lookup?
Thanks in advance.
Best Regards,
Jason
Message was edited by: Jason Wang

Hi,
I'm not sure if this is what you are looking for but
check the link "Using Resource Adapter to Obtain Connection" on this site:
http://help.sap.com/saphelp_nw04/helpdata/de/89/b262427a65423f87706a0e3faea00d/frameset.htm
Hope it helps,
Christian

Is it possible Mail - PCK -File Scenario?

Hi all,
i want to try the scenario in PCK where the mail adapter of PCK will pick the mail from mail server address and it will pass through PCK to the File receiver adapter.
anyone have a related document for this scenario.
Thanks
Ashwin

Hi
PCk -with out XI???
PCk is nothing but enables smaller companies to exchange xml documents with business parter's SAP XI
Business system environment of small business partner is connected via PCk to integration server by means of XI
check this for PCK info
/people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-1
/people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-2
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/content.htm
Message was edited by:
Anu Ram
Message was edited by:
Anu Ram

IDoc-to-File scenario with external Partner ... PCK necessary?

Hi all,
I have a question concerning to a IDoc-to-File Scenario with an external Partner. Here is a short Description of the Scenario:
The SAP ERP System creates an IDoc which should be send to the SAP Integration Server. The Integration Server respectively the IDoc-Adapter transform the IDoc in IDoc-XML. The Integration Server executes a Mapping and so on. In the final step the Integration Server should send the XML-File to a FTP Server in New York (external Partner) with the File/FTP-Adapter.
Have I to install the Partner Connectivity Kit at a Server in New York or is it working without the PCK? Which are my possibilities?
Thanks for your help
with kind regards
Christopher

Hello,
If the FTP server has connectivity to XI and if the
port is open XI can directly do the FTP using File
Adapter.
Thanks,
Himadri
Hi,
thanks for your quick answer.
What means "connectivity to XI"? Our SAP-Environment is in Germany and the FTP-Server is in New York. Is it enough to open the port in the firewall?
Thanks for your answer
Christopher Kühn

PCK XI adapter - ABAP Proxy to File Scenario How to?

Hi there,
We want to implement the following sceanrio; SAP ABAP outbound proxy to Flat-File scenario. A (sender) SAP system will trigger an outbound proxy which will send outbound data to a (receiver)file system via the PCK and Central Integration Server.
SAP (ABAP proxy) -> PCK-> XI -> File System
My question is; The PCK documentation suggests that the XI adapter included in the PCK can only be used to send/forward messages to the central integration server.
Does that means that one cannot use the same XI adapter on the PCK to redirect ABAP proxy messages to the Integration server?
Thanks,
Roberto

The PCK cannot be used as a replacement for XI Integration server. PCK is only a type of adapter engine that can run independantly. It is intended for partners who cannot use XI server. So PCK can not in itself execute interfaces. It can just forward all the messages received to the XI Integration server. PCK can only run your sender or receiver adapter all the mappings can only be executed on the integration server. So PCK just converts from the native format to XI format and forwards to the Integration Server.
Hope that carifies your question .
Thanks,
Kalyan Musunuri

Advantages of using PCK over normal XI adapters

Hi Gurus,
We are in a situation where in we need to choose either implementing PCK or a complete XI . We are a medium sized manufacturing company who need to talk to customers and vendors who already have XI.
Please let me know what are the advantages and disadvantages of implementing a PCK over a full blown XI .
Should we implement XI itself or a PCK would suffice our needs.
Thanks
Rupendra Seemakurti

Hi Rupendra,
Please check these links and weblogs on PCK...
http://help.sap.com/saphelp_nw04/helpdata/en/99/115281baba404890d2561617a78409/content.htm
/people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-1
/people/siva.maranani/blog/2005/08/30/pck-cross-sectional-analysis-part-2
Regards
Anand

Module Development using PCK

Hi All,
I have to develop a module for the file adapter. I have installed the PCK (Partner Connectivity Kit) and the related development environment. I just need to test the module for the Receiver File Adapter. But how can this be done using PCK. What should be the minimum things required? Are there any articles or help available?
Thanks,
Sandeep

http://help.sap.com/saphelp_nw04/helpdata/en/8b/895e407aa4c44ce10000000a1550b0/frameset.htm
The PDF
How To Create Modules for the J2EE Adapter Engine
available at service marketplace
https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
Should help you!!!
Regards,
Amol
Message was edited by: Amol Joshi

SP9 on PCK - file adapter configuration or Messaging System Test

Hi,
I have upgraded my XI 3.0 PCK from SP1 to SP9. This is fine but now I do not have the Messaging System Test JSP
(I could not install the old one).So I would like to
configure the file adapter to send to my adapter some outbound messages.
I have tried configuring the file adapter as
I do on full XI server but the file adpater on PCK
just doesn't want to recognize the binding. No error logs, nothing. Any ideas what could be wrong ?
Sincerely,
Maxim Naidenov

The configuration of the PCK is different to the XI.
You need:
Communication Channel:
-> for Sender (File)
-> for Receiver (XI) (Here you enter the URL of the XI)
sender agreement (matching sender channel and interface)
receiver agreement (matching receiver channel and interface)
As the XI needs the same configuration for partner and service as the PCK, you should create two partners for PCK and XI and assign the sender channel to the service belonging to the partner PCK and the receiver channel to the service belonging to the partner XI.
I hope that helps
Stefan

Configuring PCK

We are trying to set up PCK. We configured the sender party, service (abstract service) and sender agreement / receiver agreement in PCK.
We didn't create any colloboration agreements in integration server..(Though we set up the party/service in XI server)
We were expecting the message to fail with in the integration server, but our sender CC itself fails in adapter monitor with error,
<i>Error: ConfigException: No XI receiver agreement configured in PCK for XI message header</i>
Anybody know what we are missing? Is our expectation that message will go to integration server and fail there wrong?

What communication channel did you use for sender/receiver? The receiver cc must of type XI.
And you need party/service for the receiver as well as for the sender.
Look here for more details:
http://help.sap.com/saphelp_nw04/helpdata/en/32/a63d40c6d98437e10000000a155106/frameset.htm
Regards
Stefan

SOAP Adapter in PCK

Hi,
I am trying to get the SOAP Adapter in the PCK running, but always get an error while sending a SOAP message to the adapter. I configured the send adapter as described under help.sap.com and when I try to check the availability of the channel by accessing the url
http://localhost:50000/XISOAPAdapter/MessageServlet?channel=PartyA:SOAPService:soapchannel.
I always get the following Error:
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
The file adapter is working without any problems.
Can anyone tell me what I am doing wrong?
Regards,
Ulf

Hello Hans Christian,
thank you for your reply. The Helper Servlet returns the following:
<?xml version="1.0" ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>748d6d504759d17c711b6540538844c3</channelID>
<name>soapchannel</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party>PartyA</party>
<service>SOAPService</service>
</s:ChannelInfo>
I think my problem might have something to do with jndi, because it seems, that the ModuleProcessorBean can not be found (The message servlet returns "ModuleProcessorLocal not instantiated" and when I look in the server log files there is also a NameNotFoundException during the lookup of ModuleProcessorBean.) Could this have something to do with my problem?
I am now trying to update the WebAS and PCK to the latest support package and hope, that this helps somehow.
Thanks in advance for any further help.
Regards,
Ulf

SCCM 2012 and .PCK files - how exactly are they used?

Ok, no one, not even Microsoft engineers can seem to provide a clear and definitive answer on this topic, everyone's understanding of the .PCK file with relation to SCCM 2012 is clear as mud.
I understand what .PCK files are...in the SCCM 2007 world, and how they work, all that jazz, what I don't understand is how/when/why they would be used by SCCM 2012...it seems that sccm 2012 would only need these .pck files during a reassignment of a shared
DP in a migration scenario...even that surmise is sketchy since I've watched very closely the DP content conversion process and at
no time did the server access the .PCK files to populate the single instance store.
I am going to do some more testing on my own, my ultimate goal is to permanent delete the contents (not the folder itself) of the SMSPKG folder, essentially all the .PCK and .DL$ files to save space on my server.
If any soul out there knows..not guesses...the purpose of the .PCK file in 2012, let me know please, don't just copy/paste other people's posts as an answer, explain in clear terms each step of the process that 2012 would utilize a .PCK, or if the answer
really is that 2012 does not use .PCK files at all, let me know.
I have a single primary site with 16 secondary sites in my SCCM 2007 environment, I'm migrating to a single primary with 16 distribution points...so even if .PCK's are used to populate secondary sites, I should not need them since I won't have any secondary
sites once all of my DP's are migrated...yeah?
Thanks!
Terry

Thanks for the reply Torsten, that would make sense if my primary site had any .pck files at all (my sccm 2012 site that is) only my DP's have .pck files. I have no child sites in my 2012 hierarchy unless DP's are child sites (I thought secondary sites are
child..) When my DP's require a package they get them from my primary site, not other DP's. I have no 'Pull' DP's setup.
If SCCM 2012 uses a 'single instance store', which contains 3 folders itself that seem to contain compressed versions of the package files, then there should be no need for another folder that also contains compressed files...just a thought.
Terry

RFC sender in PCK

Hi Experts,
I have this proposed scenario:
RFC -> PCK -> PI -> HTTP server
To do so, I trying to configure the PCK to receive the RFC sender message and forward it to de PI.
I created in PCK a Party with empty name and two services, one for the ECC sender (RFC) with it's name and other with empty name for the PI receiver.
The communication channels and its agreements were configurated to only forward the received message to PI. I don't find any errors on them.
When I run the RFC, I am receiving this error:
Error in processing caused by: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=DE1;TS=;AN=ZTI_RFC_PI;ANS=urn:sap-com:document:sap:rfc:functions; caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=DE1;TS=;AN=ZTI_RFC_PI;ANS=urn:sap-com:document:sap:rfc:functions;
Do you have any ideia about what can be wrong? Wich component should I check?
I can simple forward the RFC message to the PI or I should map it to another format? If I have to map, how can I import it's definitions to PCK?
Thanks anyway,

Hi Stefan,
The agreements already had the receiver information.
Anyway, the party and the service were recreated with diferent names. After that, the sender and receiver agreements were also recreated. But, another error began to occur:
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found:
lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND,
fromParty '', fromService 'DE1', toParty '', toService '', interface 'ZTI_RFC_PI', NS 'urn:sap-com:document:sap:rfc:functions'
for channel 'CC_Sender_RFC_ECC' (channelId 5aa283a1c598bb6be787eeb6460772f8)
I think that's related to the RFC message header, that contains the receiver service and party empty, as seen in the error message (toParty '', toService '').
But if I create a party and service with empty names the previous error occurs again.
Any ideia about how to deal with RFC sender in PCK?

XI PCK 3.0 fails during installation

Hi,
during the installation of the XI PCK Version 3.0 the installtion fails with an error.
Here is a dump from the installtion log:
05/03/10 11:07:25 - ERROR: Not deployed. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application sap.com/com.sap.xi.mdt..
                     Reason: Cannot parse ejb-j2ee-engine.xml.; nested exception is:
                          com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: Cannot parse ejb-j2ee-engine.xml.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:477)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
                          at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
                          at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
                          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:94)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
                     Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: Cannot parse ejb-j2ee-engine.xml.
                          at com.sap.engine.services.ejb.deploy.xml.InqmyEjbParser.parseXml(InqmyEjbParser.java:86)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:334)
                          at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:252)
                          at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2057)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:594)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:365)
                          at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:296)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:290)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:321)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3028)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:462)
                          ... 10 more
                     Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7) -> com.sap.engine.lib.xml.parser.NestedSAXParserException: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)(:main:, row=1, col=7) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:7)
                          at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:131)
                          at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:117)
                          at com.sap.engine.services.ejb.deploy.xml.InqmyEjbParser.parseXml(InqmyEjbParser.java:81)
                          ... 20 more
                     For detailed information see the log file of the Deploy Service.
Is there really a bug in the ejb-j2ee-engine.xml - File ?
Did anyone have similiar problems ?
Any help is greatly appreciated.
Cheers,
Frank

Hi Frank,
we also have encountered this problem.
This the problem with the XML File. XML File is not properly formed.
You have to search for the mdt.sda file becuase during installation it hangs up during the deployment of mdt.sda file and then you can look for xml file in at mdt.sda file.
This problem comes because of the SPACE are there in the XML file.
This would resolve your problem.
Regards,
Alok Sahu

Adapter development in PCK in a one2many scenario

Hello,
I want to develop my own adapter. To do that I installed the PCK and changed the relevant parameters as described in the help to pass the test messages through the PCK.
Before changing the sample adapter I tested a one2one scenario without problems.
But now to my question: is it possible to habe only one sender and two receiver in this PCK test scenario (one2many)? Is there a possibility to duplicate the incoming message to more than one receiver?
Kind regards,
Daniel

Hello,
I want to develop my own adapter. To do that I installed the PCK and changed the relevant parameters as described in the help to pass the test messages through the PCK.
Before changing the sample adapter I tested a one2one scenario without problems.
But now to my question: is it possible to habe only one sender and two receiver in this PCK test scenario (one2many)? Is there a possibility to duplicate the incoming message to more than one receiver?
Kind regards,
Daniel

PCK in XI

Similar Messages

Maybe you are looking for