RfcAdapter-Reciver error in channel GeneratedReceiverChannel_RFC

Hi all,
We had setup up ALM in XI/PI, sometime we receive alert with below content:
Blank in below fields:
SXMS_ERROR_CODE, SXMS_ERROR_CAT, SXMS_MSG_GUID
SXMS_FROM_SERVICE, SXMS_FROM_INTERFACE, SXMS_TO_INTERFACE
Have values in below fields:
SXMS_TO_SERVICE = QA3CLNT100 (the ERP side business system)
SXMS_TO_ADAPTER_TYPE = RFC
SXMS_TO_ADAPTER_ERRTXT = RfcAdapter-Reciver error in channel GeneratedReceiverChannel_RFC: can not instan
Except this alert message, there is nothing wrong on message processing between XI/PI and ERP. May I know is this an alert about temporary error (outage) on communication channel when ERP is performing short maintenance task? If yes, can this sort of alert be avoided? Thanks.
Regards,
Donald

Hi,
you can modify your alert rule for throwing alert only on msg mapping error on integration engine........in this way, no alert will be generated when your ERP system is under modification but in this case, no error will be generated if there is any error in your reciver RFC comm channel........i think you will get error only if ERP is down, once your RFC comm chanel parameters are okay in the initial configuration..... so for ERP down error, you can configure CCMS and get an alert for it.............in this way, you can avoid the above type of alert for your reciver RFC comm channel.......
Regards,
Rajeev Gupta

Similar Messages

Error during channel initialization

Hi all,
Iam trying JMS->XI->FILE scenario. Iam using sonicMQ and have finished the scenario. I have added sonic-client.jar in the provider.xml and deployed the required sda file. Now when i try to execute the scenario iam getting the following error in communication channel monitoring.
Error during channel initialization...
Can anyone throw some light on how to solve this error.Any help on this will be appreciated.
Regards,
Sudheer.

HI,
I have looked at the log file at the location specifies by you. Even there it says the same thing.Iam not able to figure out any thing from it.Please tell me if you know about it.
#1.5#00163500DB18004B000000980000250C000416D019B37FA6#1150982947104#/Applications/ExchangeInfrastructure/AdapterFramework/Services/JMS_ROOT##com.sap.aii.af.service.jms.WorkerImpl.start()#J2EE_GUEST#0####148d320201f311db8f6900163500db18#output##0#0#Error#1#com.sap.aii.af.service.jms.WorkerImpl#Java###Channel is errornous, hence it cannot be started. See error messages (' Error during channel initialization; exception trace: ') before. Reconfigure it or restart the JMS service!#1#JMS_in_SimpleMessage#
Regards,
Sudheer.

HT3702 I can't contact itunes store. And I recived error messages: Please iTunes support to complete iTunes

I can't contact itunes store. And I recived error messages: Please iTunes support to complete iTunes ID [email protected]

You will need to do what it says, contact iTunes Support. These are user-to-user support forums, if you thought you were contacting Apple by posting here. Go here:
http://www.apple.com/emea/support/itunes/contact.html
to contact the iTunes Store.
Regards.

I recived "error 16" to star edge animate

I recived "error 16" to star edge animate

Hi ,
This error means that the permissions to the application folder is set incorrectly.Take a look at this link : Configuration error 16 | CC, CS
Thanks and Regards,
Sudeshna Sarkar

Reciving error code 205

I am trying to up dater but can't recive error code 205

Hi Golly,
You can follow the article: Error downloading, installing, or updating Creative Cloud applications to get your issue fixed.
You can also follow the thread: Creative Cloud App, installation error code 205 where this issue is already discussed and stands resolved.
Let us know if it works or not.
Thanks,
Ratandeep Arora

BEA-380000: General runtime error: Read channel closed - intermittent

I am encountering this error code intermittently. My production has been live from past 20 months and I see this error very recently and its like once a week.
I doubt if this has something to do with the network and as this is very generic error(BEA-380000) I am not able to find any pointers on this error.
My environment
Solaris 10,Weblogic 10.3(Not clustered)
fault="<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382500</con:errorCode>
<con:reason>OSB Service Callout action received SOAP Fault response</con:reason>
<con:details>
<con1:ReceivedFaultDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Server</con1:faultcode>
<con1:faultstring>BEA-380000: General runtime error: Read channel closed</con1:faultstring>
<con1:detail>
<con:fault>
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>General runtime error: Read channel closed</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</con1:detail>
</con1:ReceivedFaultDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>"
Cheers
Sridhar

Matt,
How are you invoking local proxy from HTTP proxy (using route node or service callout)? Is local proxy calling another proxy/business service? Do you have fault handling implemented?
Can you also check server log to figure out any additional error information (like stacktrace)?
Regards,
Anuj

ISA iviews error in Channel Management Portal for partner portal

I am getting the following error while accessing any iview which uses the GenericISAComponent or GenericICSSComponent in the Partner Portal. I am using CRM 5.0 and SAP Portal 7.0 (2004s). What configuration needs to be done in order to make ISA iviews to work? If you have a link/document to configure ISA in the partner portal, please send me. I am using SAP provided business package for channel management. Any help is appreciated.
Errors displayed in the portal:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.crm/com.sap.pct.crm.roles/com.sap.pct.crm.partnermanagercc/com.sap.pct.crm.chm.pmc.shop_management/com.sap.pct.crm.chm.isa.pmc.product_catalog
Component Name : com.sap.pct.crm.app.channelmgmt.GenericISAComponent
The exception was logged. Inform your system administrator..
Exception id: 06:45_07/08/07_0075_13177350
See the details for the exception ID in the log file
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/specialist/com.sap.pct.crm/com.sap.pct.crm.roles/com.sap.pct.crm.partnermanagercc/com.sap.pct.crm.chm.pma.service_center/com.sap.pct.crm.chm.isa.service
Component Name : com.sap.pct.crm.app.channelmgmt.GenericICSSComponent

I am still working on this one, but I think I ca help you a bit on the way.
Keywords: EP7, ISA CRM 5.0
When deploying BP for CRM in the portal the permissions on the component is set for the super_admin_role to be the owner.
If you check the super_admin_role and assigned action you will find the Action : AclSuperUser.
As a test you can assign this action, AclSuperUser, to the role you are using and it should work.
For production purposes I can not recommend to use AclSuperUser action to a normal user since this is very powerful action. I'm currentley investigation how to assign minimal permissions for the role I'm using to make the GenericICSSComponent work.
Best Regards
Jan-Erik Hov

Error: The channel class 'mx.messaging.channels.AMFChannel' specified was not found

Hi guys. I'm stuck with the class not found error trying to use remote objects with BlazeDS. I'm building the application using flex sdk 3, Ant flexTasks.jar (without FlexBuilder) and Tomcat 5.5.17. The result after clicking on the Remote service button is a window with the following error message: [MessagingError message='The channel class 'mx.messaging.channels.AMFChannel' specified was not found.'] In my code, I have in main.mxml: <?xml version="1.0" encoding="utf-8"?> <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"layout="vertical"> <mx:Script>..CDATA[import mx.controls.Alert;..</mx:Script> <mx:RemoteObject id="remObj" destination="product" result="Alert.show(event.result.toString());" fault="Alert.show(event.fault.faultString);"/> <mx:Button id="remoteService" label="Remote Service" click="remObj.getResults('MyName');"/> </mx:Application> In remoting-config.xml: <?xml version="1.0" encoding="UTF-8"?> <service id="remoting-service" class="flex.messaging.services.RemotingService"> <adapters> <adapter-definition id="java-object" class="flex.messaging.services.remoting.adapters.JavaAdapter" default="true"/> </adapters> <default-channels> <channel ref="my-amf"/> </default-channels> <destination id="product" channels="my-amf"> <properties> <source>flex.example.ProductService</source> <scope>application</scope> </properties> <adapter ref="java-object"/> </destination> </service> In java: package flex.examples.ProductService; public class ProductService{ public String getResults(String name) { String result = null; result = "Hi " + name + ", this is a service and the time now is : " + new Date(); return result; } } The services-config.xml is a standard like delivered within blazeds.war. My guess is that something is wrong is with the compilation. My Ant compile task looks like: <target name="compile_flex_examples"> <mxmlc file="${param1}" keep-generated-actionscript="true" context-root="${app.name}" services="${webinf}/flex/services-config.xml"> <compiler.library-path dir="${FLEX_HOME}/frameworks" append="true"> <include name="${webinf}/lib/" /> </compiler.library-path> <compiler.library-path dir="${FLEX_HOME}/frameworks" append="true"> <include name="libs/flex.swc" /> <include name="libs/rpc.swc" /> <include name="libs/utilities.swc" /> <include name="libs/fds.swc" /> </compiler.library-path> <load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/> <source-path path-element="${FLEX_HOME}/frameworks"/> </mxmlc> </target> Any idea why Flex can not find the mx.messaging.channels.AMFChannel class? Any hint very appeciated. Thanks in advance. Devus

Did you have figure out the problem to this?
I am getting the same error message. I had two interdependant applications that were working fine when I specify a service-config.xml file at compire time. However when I try to dynamiclly configure the services at runtime, one application works, but the other doesn't. I'm not sure why mx.messaging.channels.AMFChannel is available in the one app, but not the other.
Any pointers???

Ftp error (communcation channel

hi we are getting the folowing error when we monitor a communication channel can any one help me regarding this
An error occurred while connecting to the FTP server 'abcdeg.ee.yyyyy.xx:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 530 Login incorrect.'. For details, contact your FTP server vendor.

Sandeep, you don't need to change nothing in your scenario.
As was already suggested - try to connect to that FTP server with other tool. You can try also windows console.
Also check the computer, where are you trying to connect to, if it is the right one (IP).
Do you use some special character in you password or username?
Is the userename and password set up properly regarding to case-sensitiveness?
Try following:
run the windows console (Start->Run->cmd (command)). then FTP <ftp_servers_ip> ,,,provide username, password.. connected successfully?
If yes, write first username and password in notepad and then COPY it to text box in CC definition. This will ensure no mistake in provided logon details.
Peter

SOAP Client Error:- INVALID CHANNEL

Dear Friends,
 I am configuring a simple SOAP to RFC syn scenario .
after generating the wsdl when I am testing it using SOAP UI the following error is thrown:-
!!!!!1<SOAP:Fault>
 <faultcode>SOAP:Server</faultcode>
 <faultstring>Server Error</faultstring>
 <detail>
 <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
 <context>XIAdapter</context>
 <code>Exception</code>
 <text>java.lang.Exception: invalid channel (party:service:channel) = <null>
As a part of debugging i tried to test my sender channel :-
using this URL "http://sapxi:50000/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:JEEVANBS:SOAPTORFC_SENDER_CC"
In respose I got
<?xml version="1.0" ?>
- <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>f5c38e38b7b239b8a1a2e3cfbb70b72a</channelID>
<name>SOAPTORFC_SENDER_CC</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>JEEVANBS</service>
</s:ChannelInfo>
No wi think my Sender Channel is fine;
The URL is used in generating WSDL is:-Link:[http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?
channel=:<service>:<channel>]
and by tring the same in the browser i am getting
(MessageServlet OK ).
Now i dont understand where I went wrong.
Please help.
Jeevan.

http://<host>:<port>/CPACache
CPA Cache: Monitoring
View cache update history
Current CPA cache service initialization: DIRECTORY
DISPLAY CACHE CONTENT
CPAObject: (Channel) keys: ObjectId=09c2240d575430f7a460ff5a1c18f682 values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.counterSeparator</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.counterFormat</Name><Value dataType="xsd:string">00000</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.targetFileName</Name><Value dataType="xsd:string">RECEIVER.XML</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterMode</Name><Value dataType="xsd:string">immediately</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.targetDir</Name><Value dataType="xsd:string">C:/TEMP</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.writeMode</Name><Value dataType="xsd:string">addTimeStamp</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.overwrite</Name><Value dataType="xsd:boolean">1</Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.counterStep</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=FILE_RECEIVER_CC
CPAObject: (Channel) keys: ObjectId=fc51c44174c739fbbf3ce80867e9e7c4 values: FromPartySchema= Direction=I Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.processingLocked</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.processingOrder</Name><Value dataType="xsd:string">byName</Value></Attribute><Attribute xmlns=""><Name>file.checkFileModification</Name><Value dataType="xsd:string">0</Value></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">inactive</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.sourceFileName</Name><Value dataType="xsd:string">sender2.xml</Value></Attribute><Attribute xmlns=""><Name>file.pollInterval</Name><Value dataType="xsd:string">30</Value></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.additionalPayloads</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.archiveDir</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.retryInterval</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.archiveWithTimestamp</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.sourceDir</Name><Value dataType="xsd:string">c:/temp</Value></Attribute><Attribute xmlns=""><Name>file.processingMode</Name><Value dataType="xsd:string">delete</Value></Attribute><Attribute xmlns=""><Name>file.qualityOfService</Name><Value dataType="xsd:string">EO</Value></Attribute><Attribute xmlns=""><Name>file.addPayloadNames</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.queueName</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.pollIntervalMsecs</Name><Value dataType="xsd:string"></Value></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=sender_file2
CPAObject: (Channel) keys: ObjectId=f5c38e38b7b239b8a1a2e3cfbb70b72a values: FromPartySchema= Direction=I Party= EngineType=CA MsgProtVers= AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=SOAP EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=SOAP Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>PersistDuration</Name><Value dataType="xsd:timePeriod">2592000000</Value></Attribute><Attribute xmlns=""><Name>isMessageSecurity</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>XMBWS.UseEncoded</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>XMBWS.KeepAttachments</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>XI.Interface</Name><Value dataType="xsd:string">SOAPTORFC_SENDER_MI</Value></Attribute><Attribute xmlns=""><Name>XMBWS.UseQueryString</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>XI.QueueName</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>XI.QualityOfService</Name><Value dataType="xsd:string">BE</Value></Attribute><Attribute xmlns=""><Name>XI.InterfaceNamespace</Name><Value dataType="xsd:string">http://soap_to_rfc</Value></Attribute><Attribute xmlns=""><Name>XMBWS.KeepHeaders</Name><Value dataType="xsd:boolean">0</Value></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=SOAP Channel=SOAPTORFC_SENDER_CC
CPAObject: (Channel) keys: ObjectId=3cc5f044fc4b3ec09ff525970087d20c values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.counterSeparator</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">inactive</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.counterFormat</Name><Value dataType="xsd:string">00000</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.targetFileName</Name><Value dataType="xsd:string">receiver2.xml</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterMode</Name><Value dataType="xsd:string">immediately</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.targetDir</Name><Value dataType="xsd:string">c:/temp</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.writeMode</Name><Value dataType="xsd:string">addTimeStamp</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.overwrite</Name><Value dataType="xsd:boolean">1</Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.counterStep</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=receiver2_file_cc
CPAObject: (Channel) keys: ObjectId=06316b8e39743e149b7d4984d85d7a76 values: FromPartySchema= Direction=I Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.processingLocked</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.processingOrder</Name><Value dataType="xsd:string">byName</Value></Attribute><Attribute xmlns=""><Name>file.checkFileModification</Name><Value dataType="xsd:string">0</Value></Attribute><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.pollInterval</Name><Value dataType="xsd:string">20</Value></Attribute><Attribute xmlns=""><Name>file.sourceFileName</Name><Value dataType="xsd:string">SENDER.XML</Value></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.additionalPayloads</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.archiveDir</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.archiveWithTimestamp</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.retryInterval</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.sourceDir</Name><Value dataType="xsd:string">C:/TEMP</Value></Attribute><Attribute xmlns=""><Name>file.processingMode</Name><Value dataType="xsd:string">delete</Value></Attribute><Attribute xmlns=""><Name>file.qualityOfService</Name><Value dataType="xsd:string">EO</Value></Attribute><Attribute xmlns=""><Name>file.addPayloadNames</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.queueName</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.pollIntervalMsecs</Name><Value dataType="xsd:string"></Value></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=FILE_SENDER_CC
CPAObject: (Channel) keys: ObjectId=f311e58a8d643de698d69aa267c22966 values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers= AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=RFC EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=RFC Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>repository.QoP</Name><Value dataType="xsd:string">open</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>messageServer</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>loadBalancing</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>logonLanguage</Name><Value dataType="xsd:string">EN</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>maxPoolSize</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>logonUser</Name><Value dataType="xsd:string">SAPUSER</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.systemID</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonLanguage</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>QoP</Name><Value dataType="xsd:string">open</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>systemNumber</Name><Value dataType="xsd:string">00</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>serverProgramID</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>systemID</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.SNCPartnerName</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.authenticationModeBasicSNC</Name><Value dataType="xsd:string">basicSAP</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>externalServer</Name><Value dataType="xsd:string">SAP</Value></Attribute><Attribute xmlns=""><Name>repository.messageServer</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>serverGatewayService</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>additionalParameter</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>logonGroup</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonGroup</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>serverGatewayHost</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>logonClient</Name><Value dataType="xsd:string">800</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>logonPassword</Name><Value isPassword="true" encryption="hw" dataType="xsd:string">AUNENT0wOj0=</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.loadBalancing</Name><Value dataType="xsd:boolean">0</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonPassword</Name><Value isPassword="true" encryption="hw" dataType="xsd:string">AQ==</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>applicationServer</Name><Value dataType="xsd:string">RRM</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>SNCPartnerName</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.additionalParameter</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>repository.logonUser</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>messageServerService</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.applicationServer</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.messageServerService</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.logonClient</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.systemNumber</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>repository.additionalRepository</Name><Value dataType="xsd:boolean">0</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>authenticationModeBasicSNC</Name><Value dataType="xsd:string">basicSAP</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=RFC Channel=SOAPTORFC_RECEIVER_CC
CPAObject: (Channel) keys: ObjectId=d8b2da4e236131e594ea8b9305a65a7c values: FromPartySchema= Direction=O Party= EngineType=CA MsgProtVers=3.0.0527 AdapterNamespace=http://sap.com/xi/XI/System ToPartyAgency= TransProt=File EngineName=af.erp.sapxi Service=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 TransProtVers= AdapterType=File Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>file.adapterStatus</Name><Value dataType="xsd:string">active</Value></Attribute><Attribute xmlns=""><Name>file.counterSeparator</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterFormat</Name><Value dataType="xsd:string">00000</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.execute</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.type</Name><Value dataType="xsd:string">bin</Value></Attribute><Attribute xmlns=""><Name>file.targetFileName</Name><Value dataType="xsd:string">IDOC.XML</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.counterMode</Name><Value dataType="xsd:string">immediately</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.writeMode</Name><Value dataType="xsd:string">addTimeStamp</Value></Attribute><Attribute xmlns=""><Name>file.targetDir</Name><Value dataType="xsd:string">C:/TEMP</Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>file.overwrite</Name><Value dataType="xsd:boolean">1</Value></Attribute><Attribute xmlns=""><Name>file.encoding</Name><Value dataType="xsd:string"></Value></Attribute><Attribute xmlns=""><Name>file.advanced</Name><Value dataType="xsd:boolean">0</Value></Attribute><Attribute xmlns=""><Name>file.counterStep</Name><Value dataType="xsd:integer">1</Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ToPartySchema= FromPartyAgency= MsgProt=File Channel=RCV_FILE_IDOC_CC
CPAObject: (Binding) keys: ObjectId=e05905bf213f3b3cbb6c441ddbd72c0a values: Direction=I ActionNamespace=http://flie_to_file_2 ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=sender1_mi AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=fc51c44174c739fbbf3ce80867e9e7c4
CPAObject: (Binding) keys: ObjectId=03109a4771e83c639ca0dc1263d49be5 values: Direction=O ActionNamespace=http://file_to_file ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=FILE_IN_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=09c2240d575430f7a460ff5a1c18f682
CPAObject: (Binding) keys: ObjectId=08cf01c7cb1a3b0fa0fd0d0f4023279b values: Direction=O ActionNamespace=http://Training/file_to_file ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=RECEIVER_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=09c2240d575430f7a460ff5a1c18f682
CPAObject: (Binding) keys: ObjectId=91652630b1eb33d88757e17b714a3c04 values: Direction=I ActionNamespace=http://soap_to_rfc ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=SOAPTORFC_SENDER_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=SOAP MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData><Attribute xmlns=""><Name>wsse.namespace</Name><Value dataType="xsd:string">http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd</Value></Attribute><Attribute xmlns=""><Name>verifySignatureKeyStore</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>verifySignatureIssuerDN</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute><Attribute xmlns=""><Name>verifySignatureSubjectDN</Name><Value dataType="xsd:string"></Value><Flag>nonTransportable</Flag></Attribute></AdapterTypeData> ChannelId=f5c38e38b7b239b8a1a2e3cfbb70b72a
CPAObject: (Binding) keys: ObjectId=e8bb20ce05103c18834ae4c226bed7c7 values: Direction=I ActionNamespace=http://file_to_file ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=FILE_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService= AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=06316b8e39743e149b7d4984d85d7a76
CPAObject: (Binding) keys: ObjectId=2b26714c0b85307981f91ffc66f18006 values: Direction=O ActionNamespace=http://flie_to_file_2 ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=receiver1_mi AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=3cc5f044fc4b3ec09ff525970087d20c
CPAObject: (Binding) keys: ObjectId=9d0a49a48df33131ad80937d45bc4d49 values: Direction=O ActionNamespace=http://soap_to_rfc ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=SOAPTORFC_RECEIVER_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=JEEVANBS AdapterType=RFC MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=f311e58a8d643de698d69aa267c22966
CPAObject: (Binding) keys: ObjectId=0cb0b225a81a3824b6da3e22e3a07a87 values: Direction=O ActionNamespace=http://IDOC_TO_FILE ToParty= FromParty= HeaderMappingConfig=null MappedActionNamespace=null MappingClassName=null ActionName=IDOC_TO_FILE_MI AdapterNamespace=http://sap.com/xi/XI/System MappedActionName=null ToService=JEEVANBS AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 FromService=SAPRRM AdapterType=File MappingId=null Attributes=<?xml version="1.0" encoding="UTF-8"?><AdapterTypeData></AdapterTypeData> ChannelId=d8b2da4e236131e594ea8b9305a65a7c
CPAObject: (Attributes:Channel:RFC:OUTBOUND) values: repository.QoP=open messageServer= loadBalancing=false logonLanguage=EN maxPoolSize=1 logonUser=SAPUSER repository.logonLanguage= repository.systemID= adapterStatus=active QoP=open systemNumber=00 serverProgramID= additionalParameterTable=com.sap.aii.af.service.cpa.TableData@136efa7 systemID= repository.SNCPartnerName= repository.authenticationModeBasicSNC=basicSAP externalServer=SAP repository.additionalParameterTable=com.sap.aii.af.service.cpa.TableData@1afe177 serverGatewayService= repository.messageServer= additionalParameter=false repository.logonGroup= logonGroup= serverGatewayHost= logonClient=800 logonPassword=AUNENT0wOj0= repository.logonPassword=AQ== repository.loadBalancing=false applicationServer=RRM SNCPartnerName= repository.additionalParameter=false repository.logonUser= messageServerService= repository.applicationServer= repository.logonClient= repository.messageServerService= repository.additionalRepository=false repository.systemNumber= authenticationModeBasicSNC=basicSAP
CPAObject: (Attributes:Binding:File:OUTBOUND) values:
CPAObject: (Attributes:Binding:RFC:OUTBOUND) values:
CPAObject: (Attributes:Binding:SOAP:INBOUND) values: wsse.namespace=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd verifySignatureKeyStore= verifySignatureSubjectDN= verifySignatureIssuerDN=
CPAObject: (Attributes:Binding:File:OUTBOUND) values:
CPAObject: (Attributes:Binding:File:OUTBOUND) values:
CPAObject: (Attributes:Channel:File:INBOUND) values: xml.documentNamespace=null ftp.user=anonymous ftp.sourceDir=null file.checkFileModification=0 file.adapterStatus=inactive ftp.processingMode=test file.addParameterParams=com.sap.aii.af.service.cpa.TableData@1fb80cf file.execute= file.sourceFileName=sender2.xml file.pollInterval=30 ftp.archiveOnFtpServer=false xml.recordsetNamespace=null file.archiveDir= file.encoding= ftp.transferMode=bin file.archiveWithTimestamp=false file.sourceDir=c:/temp file.processingMode=delete file.qualityOfService=EO ftp.anonymous=false xml.recordsetStructure=null ftp.port=21 file.advanced=false xml.recordsetsPerMessage=null file.pollIntervalMsecs= xml.keyfieldName=null file.processingLocked=false ftp.host=null file.processingOrder=byName xml.documentName=null file.type=bin file.addPayloadParams=com.sap.aii.af.service.cpa.TableData@c5bd01 ftp.password=ftp file.additionalPayloads=false file.retryInterval= xml.recordsetName=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1fbc471 file.addPayloadNames= ftp.connection=permanently file.queueName= xml.keyfieldType=StrS xml.documentSkipFirstRows=null
CPAObject: (Attributes:Channel:File:OUTBOUND) values: ftp.user=anonymous file.adapterStatus=active file.addParameterParams=com.sap.aii.af.service.cpa.TableData@1dec3f file.execute= file.targetFileName=IDOC.XML file.counterMode=immediately file.encoding= file.overwrite=true ftp.transferMode=bin ftp.anonymous=false ftp.port=21 file.advanced=false ftp.targetDir=null ftp.host=null file.counterSeparator= file.counterFormat=00000 file.type=bin file.targetDir=C:/TEMP ftp.password=ftp ftp.putSafe=YES file.writeMode=addTimeStamp ftp.writeMode=addTimeStamp file.recordsetStructure=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@814530 ftp.connection=permanently file.counterStep=1
CPAObject: (Attributes:Binding:File:OUTBOUND) values:
CPAObject: (Attributes:Binding:File:INBOUND) values:
CPAObject: (Attributes:Binding:File:INBOUND) values:
CPAObject: (Attributes:Channel:File:OUTBOUND) values: ftp.user=anonymous file.adapterStatus=active file.addParameterParams=com.sap.aii.af.service.cpa.TableData@e581c2 file.execute= file.targetFileName=RECEIVER.XML file.counterMode=immediately file.encoding= file.overwrite=true ftp.transferMode=bin ftp.anonymous=false ftp.port=21 file.advanced=false ftp.targetDir=null ftp.host=null file.counterSeparator= file.counterFormat=00000 file.type=bin file.targetDir=C:/TEMP ftp.password=ftp ftp.putSafe=YES file.writeMode=addTimeStamp ftp.writeMode=addTimeStamp file.recordsetStructure=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1a9fd8e ftp.connection=permanently file.counterStep=1
CPAObject: (Attributes:Channel:File:OUTBOUND) values: ftp.user=anonymous file.adapterStatus=inactive file.addParameterParams=com.sap.aii.af.service.cpa.TableData@145974f file.execute= file.targetFileName=receiver2.xml file.counterMode=immediately file.encoding= file.overwrite=true ftp.transferMode=bin ftp.anonymous=false ftp.port=21 file.advanced=false ftp.targetDir=null ftp.host=null file.counterSeparator= file.counterFormat=00000 file.type=bin file.targetDir=c:/temp ftp.password=ftp ftp.putSafe=YES file.writeMode=addTimeStamp ftp.writeMode=addTimeStamp file.recordsetStructure=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1d104d0 ftp.connection=permanently file.counterStep=1
CPAObject: (Attributes:Channel:SOAP:INBOUND) values: PersistDuration=2592000000 isMessageSecurity=false XMBWS.UseEncoded=false adapterStatus=active XI.Interface=SOAPTORFC_SENDER_MI XMBWS.KeepAttachments=false XMBWS.UseQueryString=false XI.QueueName= XI.QualityOfService=BE XI.InterfaceNamespace=http://soap_to_rfc XMBWS.KeepHeaders=false
CPAObject: (Attributes:Channel:File:INBOUND) values: xml.documentNamespace=null ftp.user=anonymous ftp.sourceDir=null file.checkFileModification=0 file.adapterStatus=active ftp.processingMode=test file.addParameterParams=com.sap.aii.af.service.cpa.TableData@1930d3d file.execute= file.sourceFileName=SENDER.XML file.pollInterval=20 ftp.archiveOnFtpServer=false xml.recordsetNamespace=null file.archiveDir= file.encoding= ftp.transferMode=bin file.archiveWithTimestamp=false file.sourceDir=C:/TEMP file.processingMode=delete file.qualityOfService=EO ftp.anonymous=false xml.recordsetStructure=null ftp.port=21 file.advanced=false xml.recordsetsPerMessage=null file.pollIntervalMsecs= xml.keyfieldName=null file.processingLocked=false ftp.host=null file.processingOrder=byName xml.documentName=null file.type=bin file.addPayloadParams=com.sap.aii.af.service.cpa.TableData@14a28ce ftp.password=ftp file.additionalPayloads=false file.retryInterval= xml.recordsetName=null file.conversionParameters=com.sap.aii.af.service.cpa.TableData@1bd1406 file.addPayloadNames= ftp.connection=permanently file.queueName= xml.keyfieldType=StrS xml.documentSkipFirstRows=null
CPAObject: (Service) keys: ObjectId=606ce974c84f37a983f014e1d3f6d67b values: Service=JEEVANBS Party= ServiceType=BS
CPAObject: (Service) keys: ObjectId=10c2d6f515c43629be60b9671dfb5326 values: Service=TEST Party= ServiceType=SR
CPAObject: (ServiceIdentifier) keys: ObjectId=7fe7f1f60069b2d9db121585afd90e5d values: Service=JEEVANBS Party= ServiceSchema=LogicalSystem ServiceIdentifier=
CPAObject: (ModuleSequence) keys: ObjectId=dedc7b4bb748a47830f244e3c5d79456 values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=09c2240d575430f7a460ff5a1c18f682 ModuleType=L ModuleNamespace=0
CPAObject: (ModuleSequence) keys: ObjectId=0475467f699834c80d2786ccc9281230 values: ModuleName=localejbs/RfcAFBean Position=0 ChannelId=f311e58a8d643de698d69aa267c22966 ModuleType=L ModuleNamespace=0
CPAObject: (ModuleSequence) keys: ObjectId=360f00a2a25a77f3713162c6c0aba328 values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=d8b2da4e236131e594ea8b9305a65a7c ModuleType=L ModuleNamespace=0
CPAObject: (ModuleSequence) keys: ObjectId=6a430f286f924cbb522a8b879ba0aeff values: ModuleName=localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean Position=0 ChannelId=f5c38e38b7b239b8a1a2e3cfbb70b72a ModuleType=L ModuleNamespace=soap
CPAObject: (ModuleSequence) keys: ObjectId=bf933cd5567345f2385df4854d8cfaac values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=fc51c44174c739fbbf3ce80867e9e7c4 ModuleType=L ModuleNamespace=0
CPAObject: (ModuleSequence) keys: ObjectId=96af99731794cb61b2c217c8bc8bd9c7 values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=3cc5f044fc4b3ec09ff525970087d20c ModuleType=L ModuleNamespace=0
CPAObject: (ModuleSequence) keys: ObjectId=b9a4fcf7a0d7b115b96c01cb760e459c values: ModuleName=localejbs/CallSapAdapter Position=0 ChannelId=06316b8e39743e149b7d4984d85d7a76 ModuleType=L ModuleNamespace=0
CPAObject: (AdapterTypeMetaData) keys: ObjectId=3025930377ab37a9978a279039f80b9e values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=SOAP AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=ee79718d103f3db39d8001892a09012a values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=RNIF AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=be8d625a7a143cf6b724f17ed9fc75be values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=Marketplace AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=7b88b1289df431cabbc58227fc562518 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=Mail AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=5f9815c5a6a934f8856756f25f21b552 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=BC AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=2768c3679ef9355a95a6aed25b82d230 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=XI AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=34d11731f5e43144ab4da458750d7bb4 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=CIDX AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=b4d22907ab93382bbac6321aef9f866d values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=File AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=b9d29c6630363ebba0ec15d3bc80084a values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=RFC AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=08ea74ec778939dfa31e166d4b23f357 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=JDBC AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=be9ad1ffaf643ce58ccc2fd53e7e4504 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=HTTP AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=99648243744a3efea5952abe216b49f5 values: AdapterSWCV=3b787a8035c111d6bbe0efe50a1145a5 SWCVVersion=640 AdapterType=JMS AdapterNamespace=http://sap.com/xi/XI/System SWCVElementTypeId=01200615320200005507 SWCVName=SAP_BASIS SWCVVendor=sap.com
CPAObject: (AdapterTypeMetaData) keys: ObjectId=8b95769f448d3977899254c65a2c8ec6

Error in channel

When accesing a channel created using JSPProvider i get the following error in Portal Server 6.1:
ERROR: ProviderCommands.genHelp(): can not get helpURL for: scLibraryProvider
com.sun.portal.providers.ProviderException: providerAdapter.getHelp(): com.sun.portal.providers.context.ProviderContextException: PSProviderContext.getStringProperty(): com.sun.portal.desktop.context.ContextError: DPPropertiesContext.getStringProperty(): property not found in profile for channel=scLibraryProvider, key=docroot
          at com.sun.portal.providers.ProviderAdapter.getHelp(ProviderAdapter.java:446)
          at com.sun.portal.providers.ProviderAdapter.getHelp(ProviderAdapter.java:509)
          at com.sun.portal.providers.util.ProviderCommands.genHelp(ProviderCommands.java:219)
          at com.sun.portal.providers.util.ProviderCommands.getProviderCommands(ProviderCommands.java:98)
          at com.sun.portal.desktop.taglib.container.table.GetProviderCommandTag.doStartTag(GetProviderCommandTag.java:55)

Check if the JSP Provider deployment went through
fine in the desktop.dpadmin.debug logs. That may
give u more insight.

CAN error with Channel API

Hello All,
Right now i am facing a CAN error when run my script which was developed using channel APIs. I am not able to trace out the the reason of the error. Pls find attached code and Error description. I have uploaded the sample code here and I am writing several messages in the same VI as same like in the code. Pls guide me in this
Thanks in advance
Anoop
Attachments:
CAN Channel API error.JPG ‏22 KB
Channel API test.vi ‏29 KB

Hi Anoop,
Is the code you posted the exact code you are using when you get the error? The reason I ask is, usually this error is associated with using the Set Property VI after the interface has already been started, such as in a loop.
Are you able to use any examples from the Example Finder successfully? (Help > Find Examples) You can Browse to CAN examples by clicking Hardware Input and Output > CAN > Channel API.
Hope this helps!
Adam W
Applications Engineering
National Instruments

Error in Channel / showing in Channel monitor

Hi All,
- I have a receiver channel defined with a custom XI adapter.
- The channel monitoring now says: Status=removed, Text=No adapter registered for this channel
- The consequences of this are, error in message processing
The adapter is there, but:
- I reinstalled the adapter recently, using sdm and the action sequence undeploy, deploy
Question to the experts:
- What can I do to make my new adapter version known again to my channel?
Thanks a Lot

Hi,
Hi,,
2 Introduction
Configuring IDoc adapter in Exchange Infrastructure 3.0 requires some configuration on the SAP
systems, for both XI and the backend system where the IDoc message is to be sent. These steps, although
simple, are many times missed or mis-configured, causing the delivery of messages to fail.
Since IDoc adapter uses the ABAP stack, instead of J2EE, the configuration requirements are mainly in
ABAP.
Setting up IDoc adapters requires the XI integration server to be able to communicate with the backend
SAP system, and also to make sure that the Logical System Name used when posting IDoc exists on the
backend SAP system.
3 The Step By Step Solution
The basic steps for the IDoc configuration are outline below:
1. Configure SM59 on XI to communicate to SAP backend system.
2. Configure port on XI for IDoc communication.
3. Create or verify the Logical System Name on the SAP backend system.
4. Create or verify business system in XIs System Landscape Directory.
5. Verify the Logical System Name of the business system.
6. Verify or add the Logical System Name for the sender business system.
7. Create/configure the Communication Channel for the IDoc receiver adapter
3.1 Configure SM59 on XI to communicate to SAP backend system.
1. Using transaction SM59, create an RFC destination with Connection Type = 3.
In this example, the RFC destination name is NDVCLNT510.
2. Enter the logon information:
3. Test the connection by clicking on Testing connection and Remote logon.
Both must be successful.
3.2 Configure port on XI for IDoc communication.
4. Go to transaction IDX1 on XI, and create a port. In this example, the Port name is SAPNDV.
The Port name must be in the form of SAPxxx, where xxx is the system ID of the backend SAP
system.
The Client must be the client number of the backend SAP system.
Select the RFC Destination which was created in the previous step.
3.3 Create or verify the Logical System Name on the SAP backend system.
5. Enter transaction SALE on the SAP backend system.
6. Create or verify the Logical System Name. In our example, NDVCLNT510 is verified.
3.4 Create or verify business system in XIs System Landscape Directory.
The business system name for the SAP backend system must contain a valid Logical System Name. This Logical System Name is the one verified or created in the previous step.
7. In the System Landscape Directory, select the SAP backend business system. If one does not exist, then create the business system. Verify the Logical System Name.
3.5 Verify the Logical System Name of the business system.
8. In the Integration Directory, doubleclick on the business system (in our example, it is NDVCLNT510).
Navigate the menu:
Service Adapter Specific Identifiers.
If information is empty or incorrect, then it will have to be synchronized with the content of the System Landscape Directory. Follow the steps below for synchronization.
9. (Optional) Synchronization of the business system in Integration Directory to the business system in System
Landscape Directory.
Double-click on the business system in the Integration Directory.
Switch to Edit mode.
Select menu: Service Adapter-Specific Identifiers
10. (Optional) Within the dialog box, click on the button as indicated below to resynchronize.
11. (Optional) If the expected data from the System Landscape Directory is not updated, then the SLD cache may need to be cleared first.
3.7 Create/configure the Communication Channel for the IDoc receiver adapter.
15. In the Integration Directory, create an IDoc receiver communication channel.
The RFC Destination is from step 3.1.
The Port is from step 3.2.
NOTE:
There is no need to create an IDoc sender Communication Channel for XI. Instead, the backend SAP system must be configure to send the IDoc to XI.
4 Appendix
Transaction: IDX2
There are a couple of situation where IDX2 can be useful on the XI system.
1. When we want to test connection between the XI and SAP backend system.
2. When an IDoc has changed, and the meta data stored in XI needs to be update. When an IDoc is sent from the SAP backend system to XI, XI will first check to see if the meta data for the IDoc is already in its persistent cache. If not, then XI will use the configuration in IDX1 to retrieve the IDoc meta data from the backend system. If the
meta is already in cache, then it will NOT do so. Therefore, when an IDoc has changed, it is necessary to manually update the new meta data on XI, or delete it from the cache, so that the latest version can be retrieved. IDX2 is used for this purpose.
Go to transaction IDX2 and click on Create.
Enter the IDoc Type and the Source Port as defined in step #2. Click Continue.If successful, the following will show up. If error occurs, then the IDX1 configurations will need to be re-checked.
Reward points if find useful.

Ipod touch (4th gen) is disabled and stuck on "recovery mode" and i keep reciving "error 3259" connetion time out when i restore. what should i do?

hello, i left my ipod touch connected overnight to my playstation3 to charge and the next morning i woke up to find the ipod disabled. i put it on recovery mode and tried to restore it, but everytime itunes downloads the file, a windows pop-up appears saying "network connection timed out error 3259" and now my ipod is stuck on recovery mode. what should i do ?

You posted in the iPad forum instead of the iPod forum. I'll request that Apple move your post.
iOS: Not responding or does not turn on
http://support.apple.com/kb/TS3281
iOS: Resolving update and restore alert messages
http://support.apple.com/kb/TS1275
 Cheers, Tom

ChnEnvelopes gives error "Target Channel is too short for results"

I have 3 channels (1-3) of data loaded, 1 is time, the other 2 are data channels. I am trying to run ChnEnvelopes from within VBS with this command.
call ChnEnvelopes(1,2,4,5,6,7,5)
The size of the original data is 34127.
If I use the dialog it works fine.

Hi,
When you perform calculations in DIAdem, the results will be stored in a channel in the data matrix. When you load a data file, it will occupy a channel for each data channel in the file. If the data channels in the file are longer than the maximum channel length selected in the DIAdem settings, DIAdem will use 'dynamic' channels versus the channels you have configured in the settings menu.
There are two things you can do:
1. Go to the 'Window' menu in DIAdem and select 'Close all'.
2. Then select the 'Settings' menu and choose 'Data management'.
3. Click the 'Data Matrix' button and set the maximum channel length to something larger then your channel length (i.e. >= 34,127). The default value here is 8,192.
Another way to do this is to use dyn
amic channels for the calculation, i.e. use this command:
call ChnEnvelopes(1,2,,,,,5)
Altough the result channels are shorter than 34,127, the software will use these channels for some temporary data storage.
This should hopefully work for you. Let me know if you have any additional problems or questions.
Otmar
Otmar D. Foehner
Business Development Manager
DIAdem and Test Data Management
National Instruments
Austin, TX - USA
"For an optimist the glass is half full, for a pessimist it's half empty, and for an engineer is twice bigger than necessary."

RfcAdapter-Reciver error in channel GeneratedReceiverChannel_RFC

Similar Messages

Maybe you are looking for