Reg : OS commands in Adapter Configuration

Hi,
I have seen the option like Run Operating Sustem Command Before Message processing and After Message.
How can I use them
Where can I see the results of it.
I need an OS command to diplay all the files in a directory before message processing .
How can I use it.
Regards,
Kalpana.

Hi,
Please Follow these
Run Operating System Command Before/After Message Processing -
http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
Also to catch errors - /people/michal.krawczyk2/blog/2005/08/17/xi-operation-system-command--error-catching
Reward points if Helpful
Regards
Sesha

Similar Messages

What is Operating System commands in Adapter Configuration??

Hi Frnds,
When we will use Operating system commands Option in Adapter Configuration??
Regards,
Raj

Hi,
Go through this blogs..
/people/michal.krawczyk2/blog/2005/08/17/xi-operation-system-command--error-catching
/people/sameer.shadab/blog/2005/09/21/executing-unix-shell-script-using-operating-system-command-in-xi
When we will use Operating system commands Option in Adapter Configuration??
http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/content.htm
Go through this link some experts discussions:
Run Operating System Commands
How to run Operating system command in receiver JDBC Adapter
Hope this info is useful to you..
Thanks,
Satya Kumar..

Internal LAN adapter configuration commands

Could anyone describe me the meaning of hsma
command option:
7206MEDA(cfg-lan-Token 0)#adapter 1 4000.0047.4522
7206MEDA(cfg-adap-Token 0-1)#?
Internal Lan Adapter configuration commands:
hsma Hot Standby MAC Address parameters
Thanks in advance for any information

Hi,
I have attached a document describing what hsma is all about in more detail, including sample configurations.
In very simple words. It is a mechanism, a little bit like hsrp, to allow to cip's to backup each other. You configure a virtual adapter which is always only active on one of the two cip's and they monitor each other. If one cip goes down, the other one takes over and activates the virtual adapter.
When the two cip routers were connected to a tokenring infrastructure than the redundancy whas achived by using the same mac address on the cip's reachable over to different source bridged path using different rif's.
If you connect the two cip routers via a ethernet than there is no rif field in your packets anymore, you can not do source bridging. Additional the cam table of a ethernet switch can not deal with two times the same mac address on different ports in the same vlan.
Hsma allows for a similar level of redundancy if your cip routers are connected via a ethernet backbone.
thanks...
Matthias

XI - 3.0 Adapter configuration

Hi,
can any one tell me how to confirm that XI adapters ( default ones wotever comes along with NW-XI) have been installed successfully?
Reg,
Venkat

Hi,
For IDOC ADAPTER
follow the steps:
1 Scenario
This guide deals with all the configurations required to create an IDoc adapter in Exchange Infrastructure
3.0 to send an IDoc from XI to the SAP backend system.
Unlike other types of adapters, the IDoc adapter has dependencies on the XI 3.0 ABAP configurations and
the backend SAP system configurations. Those configurations information will have to be either created
first or retrieved in order to complete the IDoc adapter configuration.
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.
2) For File and RFC follow this blog:
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Regards
Hemant
Awar points if find helpful

Adapter Configuration failed, please re run the installer to fix the issue

the above message is popping up while i try to install BODS in Windows 8 64bit
after i give ok i couldnt able to run the BODS ??

the first problem about Adapter Configuration failed during installation is a bug. This problem happens in case the installer is not able to get the short path name for LINK_DIR and while submitting the command for configuring the Adapter the command is having spaces in the path resulting in incorrect command which is failing
check the di_0.log installer log file in <BOE_HOME>\BusinessObjects Enterprise 12.0\logging folder, open this file in notepad and search for following text
com.acta.adapter.sdkutil.UpdateAdapterVersion
you will see a error like java.lang.NoClassDefFoundError: Objects\BusinessObjects
if you are not using Adapters then this is not a problem for you, your installation is fine, you should be able to use other functions
The second issue with SNMP, the error message says "The port may be in use by another process", check if the port 4001 is avilable ? try with a different port number

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

File adapter configuration parameter for "hexadecimal conversion"

(File adapter for XI 2.0)
Does anybody know the exact File adapter configuration parameters for reading a file with hexadecimal control characters as seperators. My file has
3 types of seperators - i.e "2F", "05" & "0D2F"
Eg: xml.fieldSeparator= "2F"
When I specify this the file is getting split into fields
at all the seperators in the file. I guess I am not using the right format in my defination ?
Dorai

Is there any special format for reading a file containing hexadecimal control characters?
The file to be processed has hexadecimal separators:
Field Delimiter : '09' or '05'
End of record delimiter: '0A' or '25'
End of Table delimiter : '07' or '2F'
Initially i would like to read the file into XI as it is i.e without any split by using "xml.fieldFixedLengths= "
However, everytime I process the file(with hexadecimal contol characters), I have noticed that my file is getting split, even when I did not specify anything for field separator(i.e when i used fixed field length).
Thanks,
Dorai

File name naming convention in File Adapter configuration in ID

Hi All ,
I have a query related to xml filename created in IDOC-XI-FILE scenario based on value of one of IDOC field .
The scenario is like this :
I have to send one xml file per store for material master . In this case how can I define my file name with store name in File adapter configuration in ID .
Naming convention should be
<storename>_date_masterdataname.xmlwhere store name is one of field of IDOC .
Plz help me .
Thanks in Advance
Regards
Prabhat Ranjan

Hi Prabhat,
take a look at this weblog:
/people/jayakrishnan.nair/blog/2005/06/28/dynamic-file-namexslt-mapping-with-java-enhancement-using-xi-30-sp12-part-ii
you have to specify variable substitution
(in the file adapter)
and give the path to the store name (in the variable sustitution table)
you file name schema (from the file communication channel can look like this)
%storename%_date_masterdataname.xml
Regards,
michal
Message was edited by: Michal Krawczyk

Using adapter specific message attributes in SOAP adapter configuration

Hi,
Can you please let me know how to use adapter specific message attributes in receiver and sender SOAP adapter configuration. If possible , with example.

See here:
Adapter-Specific Message Attributes in the Message Header
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/frameset.htm
Sender Soap Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
Receiver Soap Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

Sender Mail Adapter Configuration error

Hi,
I am working on scenario mail adapter to CRM system. And when I tried to configure the sender email adapter I have got the error following error, Can any one help me to resolve this issues
error occured: exception caught during processing mail message; java.net.ConnectException: Connection refused
the details I have provided are as follows
Transport protocol is POP3
URL - POP://mailservername/Inbox/folder
And I have tried with the IMAP4 also
URL - IMAP://mailservername/Inbox/folder
And we have cross checked that the XI server is able to ping that particular mail server.
Regards,
Venkat.

Hi Venkateswara,
I would suggest that you go through these to know how to configure your sender mail adapter,
<a href="/people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step mail adapter step by step</a>
<a href="/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure adapter Scenario</a>
Also, to know the various parameters of a sender mail adapter, just go through this link,
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/23/c093409c663228e10000000a1550b0/content.htm">Configuring sender mail adapter</a>
Check your mail adapter configuration against these details. Also, check if the mail server you are trying to access is running.
Also go thru this pdf to make yourself more comfortable with mail adapters.
https://websmp205.sap-ag.de/~sapidb/011000358700004556712005E/HowTo_Mail_Adapter2.pdf
Regards,
abhy

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

Mail Adapter Configuration in XI 3.0

Hi all,
i tried to set up a process using the mail adapter. Unfortunately it doesn't work. Has anyone succeeded in setting up a process with the mail adapter using POP3 and SMTP?

Hi Michael,
I did not find any documentation of the XI 3.0 mail adapter so result of practical test only for outgoing mail using SMTP:
Mail server settings:
SMTP port 8025 (you can configure any port of course)
Account demo, password test
Mail adapter configuration:
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXIMailImpl
Part 0 : common part ######
Mail.MailSubject="mail from adapter z_outmail"
Mail.MailFrom=[email protected]
Mail.MailTo=demo@<you mail server name>
XIALL or XIPAYLOAD
Mail.MessageProtocol=XIPAYLOAD
Mail.Log=1110
Part : XI client to Mail server ######
OMail.TargetURL=smtp://<you mail server name>:8025
OMail.User=demo
OMail.Password=test
The port and path where the adapter waits for XMB messages from clients.
XI.Port=8240
XI.Path=/z_outmail
It look so that there is no POP3 support, just only IMAP.
Jiri

SOAP receiver adapter configuration issue

Hi Everyone,
When I am trying to excute a sync scenario from SAP<>XI<>Webservice from Integration engine , I am getting the below error message.
Error while sending message: com.sap.aii.af.ra.ms.api.DeliveryException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Cannot process the message because the content type 'text/xml; charset=utf-8' was not the expected type 'application/soap+xml; charset=utf-8'.
In the receiver SOAP adapter, I have configured Transformation module where I kept the MessageTransformationBean in processing sequence as a priority and also provided the module configuration.
ModuleKey: transform
ParameterName: Transform.ContentType
Parameter Value: application/soap+xml;charset=utf-8.
But still get the above error message in the communication channel. I am using certificates in my configuration that were deployed in visual Admin.
In the adapter configuration, I have just provided the Target URL, Configured User Authentication, certificate authentication and SOAP action.
Can anyone help me.. how to rectify the issue.....
Thanks in advance,
Hareen

HI Hareen,
I decided to give SOAP1.2 using the standard SOAP Adapter a try
There are a few noticeable differences between the request message of SOAP1.1 and SOAP1.2
1.) SOAP 1.1 uses a different namespace from SOAP 1.2. For SOAP 1.1 it is "http://schemas.xmlsoap.org/soap/envelope/" while for SOAP 1.2 it is "http://www.w3.org/2003/05/soap-envelope".
2.) SOAP 1.2 does not use SOAPAction in its header.
3.) Content type is also different, for SOAP 1.1 it is "text/xml" while for SOAP 1.2 it is "application/soap+xml"
So a sample request for SOAP 1.1 would be like this:
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://sampleaction"
While for 1.2 it is:
Content-Type: application/soap+xml;charset=UTF-8;action="http://sampleaction"
The SOAP action is moved to the content type (experts please correct me on this).
Based on the differences, you need:
1.) Construct the correct SOAP Envelope for request message mapping and remove it for the response mapping
2.) Use MessageTransformBean to change content type
3.) Leave SOAPAction as blank
I think dynamic soap action is no longer possible because the action is hardcoded in the module configuration (please correct).
Hope this helps,
Mark

Error in Adapter Table Adapter Configuration IDM - Oracle 10g

Error in the configuration of Oracle Database Table Adapter Configuration.
Log:
2007-10-02 10:26:40,843 INFO [DBADAPTERLOGGER] DBProvisioner::createUser : DBProvisioner::createUser : userProperties is xel_usr_id#:#V04#;#xel_usr_password#:#56pddssd#;#xel_usr_status#:#1#;#xel_usr_first_name#:#Juana#;#xel_usr_last_name#:#Rengifo#;#xel_usr_group#:##;#xel_usr_title#:#Analista#;#xel_usr_dept#:##;#xel_usr_comm_lang#:##;#xel_usr_logon_lang#:##;#xel_usr_email#:[email protected]#;#xel_usr_tel_no#:#111-222-4444#;#xel_usr_time_zone#:##;#xel_usr_date_fmt#:##;#xel_usr_dec_ntn#:##;#xel_usr_role#:#System Admin
2007-10-02 10:26:40,859 INFO [DBADAPTERLOGGER] DBProvisioner::createUser : Starting time for createUser method :1191346000859
2007-10-02 10:26:40,875 ERROR [DBADAPTERLOGGER] DBSchemaErrorHandler::error : ERROR : 1:227cvc-elt.1: Cannot find the declaration of element 'xl-ddm-data'.
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'xl-ddm-data'.

Based on your error a few questions come to mind...
What does your Configuration XML file look like? It's root XML node should be xdb_app_map. Your error makes me think you may be pointing at an adapter file versus db schema mapping file.
Are you starting from one of the provided examples like OraApp1.xml? If you followed Step 3: the connector file copy instructions during deployment, you should find the samples in "OIM_home/xellerate/XLIntegrations/DBAppTables/xml/DB_Schema" Or you can search for OraApp1.xml or OraApp2.xml.
Have you configured your IT Resource with the appropriate path to the XML file? If you are on Unix it's going to be case sensitive, I can't speak for a windows path.
I hope this helps. I know I had a few challenges myself when I first took a swing at the DB Table Adapter from the 9.0.4.1 connector pack.
regards,
Jason

JDBC Adapter configuration not initialized:null

i
we have a synchronous scenario with the following adapters , RFC <> XI <> JDBC.
1.JDBC Driver installation is done
2.RFC Destination type t is done in sap(sender) system.
3.checking the jdbc in VA is done
while running it is giving the following error.
com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
where we have to initialize JDBC Adapter configuration
Thanks in advance
Prasad Nemalikanti

hi prasad
There are 2 jar files that may be missing from your SQL JDBC driver --> msbase.jar and msutil.jar, I think once you add these to the driver it might work.
also check the driver string for the SQL driver 2 parameters
i.e 'com.microsoft.jdbc.sqlserver.SQLServerDriver' now becomes
'com.microsoft.sqlserver.jdbc.SQLServerDriver'
This will solve your problem
follow this link
Re: MS SQL Server jdbc Driver installation on XI .
XI JDBC Adapter using stored procedures
thanks
sandeep
Reward points if helpful

Reg : OS commands in Adapter Configuration

Similar Messages

Maybe you are looking for