How to Debug Sample Adapter

Hi,
Is it possible to debug the sample adapter provided by SAP.Because i am deploying it through SDM and wants to debug through NDS.
regards,
Siva T.

Hi Siva,
We can certainly debug the Sample Adapter.But i am also not sure of how to do that. I also tried for that,but couldn't able to succeed.
Regards,
Gowtham K.

Similar Messages

How to debug DB Adapter

Hi,
In our production DB we have a DB Adapter (SOA Suite 10.1.3.5.0) which seems suddenly stopped polling a table for records.
For the OC4J instance i have set the following loglevels;
oracle.tip.esb.server.dispatch =FINEST
oracle.tip.esb.server.service =FINEST
oracle.webservices.management.auditing =FINEST
oracle.webservices.management.logging =FINEST
oracle.webservices.reliability =FINEST
oracle.webservices.service =FINEST
oracle.tip.adapter.db
oracle.tip.adapter.db.DBManagedConnectionFactory
oracle.tip.adapter.db.inbound
oracle.tip.adapter.db.outbound
oracle.tip.esb.server.service.impl.inadapter
oracle.tip.esb.server.service.impl.outadapter
When i disable and enable the DB Adapter "DB_IDCARD_IN" the log.xml shows me the following relevant loglines;
<MSG_TEXT>ESB-Service - Performing Endpoint Deactivation for event 0BAD9DA2CAD011DFBFA5DFF32328B9BE and WSDL location esb:///ES
B_Projects/PREABXS_ESB_VNTS_IDCARD_IN/DB_IDCARD_IN.wsdl</MSG_TEXT>
<MSG_TEXT>Creating IEsbService instance for service "DB_IDCARD_IN".</MSG_TEXT>
<MSG_TEXT>ESBActivation agent ctor for service : DB_IDCARD_IN</MSG_TEXT>
<MSG_TEXT>Activating IEsbService for service "DB_IDCARD_IN".</MSG_TEXT>
<MSG_TEXT>Activating endpoint for inbound adapter service "PREABXS.DB_IDCARD_IN".</MSG_TEXT>
<MSG_TEXT>Activate Endpoint portType: DB_IDCARD_IN_ptt</MSG_TEXT>
<MSG_TEXT>ESB-Service - Performing Endpoint Activation for operation PREABXS.DB_IDCARD_IN_RS.receive using WSDL location esb://
/ESB_Projects/PREABXS_ESB_VNTS_IDCARD_IN/DB_IDCARD_IN.wsdl</MSG_TEXT>
WSDL location: "esb:///ESB_Projects/PREABXS_ESB_VNTS_IDCARD_IN/DB_IDCARD_IN.wsdl"
portType: "DB_IDCARD_IN_ptt"
<MSG_TEXT>Resolving location for "DBIDCARDIN_toplink_mappings.xml".</MSG_TEXT>
<MSG_TEXT>Successfully finished endpoint activation for operation "PREABXS.DB_IDCARD_IN_RS.receive".</MSG_TEXT>
The opmn log shows
<2010-10-26 14:48:52,118> <INFO> <dl.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraESB - perfo
rming endpointDeactivation for portType=DB_IDCARD_IN_ptt, operation=receive
10/10/26 14:48:56 following Normal flow1
<2010-10-26 14:48:57,165> <INFO> <dl.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraESB - endpo
intActivation for portType=DB_IDCARD_IN_ptt, operation=receive
<2010-10-26 14:48:57,243> <WARN> <dl.collaxa.cube.activation> <Database Adapter::Inbound> <oracle.tip.adapter.db.inbound.IPAddrPolli
ngService getUniqueMarkReservedValue> The markReservedValue of distributed polling might not be a unique value. To make it so, you
can add the last x digits (default = 2) of the host IP address using this format for the MarkReservedValue: [original_val]${IP[-x]}
<2010-10-26 14:48:57,306> <INFO> <dl.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraESB - succe
ssfully completed endpointActivation for portType=DB_IDCARD_IN_ptt, operation=receive
The DB Adapter uses a logical delete strategy, but i do not see any rows changed to the 'reserved' value. On the MS SQL 2005 DB the DBA does see the SQL statements executed by the adapter but i can not see any response (query results). The DB Adapter uses an Connection Pool based on the com.microsoft.sqlserver.jdbc.SQLServerDriver.
How can i trace the queries and responses executed by the DB Adapter ? On the DB side, in SQL Server Profiler, i do see that the SELECT and UPDATE statements from the DB Adapter are executed, i do not know if you can see the actual query results here. But but do not see the any results in ESB or in the column used for the logical delete.
Any hints or tips ?
Cheers,
Peter

Finally the cause was a not documented clause in the adapter. The adapter was working as designed

How to Debug Idoc Adapter from XI to R/3

Hi,
Can any one please help in debugging the Idoc adapter from XI to R/3.
Here is the my problem - XI to R/3 idocs have been created correctly but the service relation ship is created incorrectly.
i.e. When XI creates inbound idoc into R/3, it is also linking some other non relevant idoc which is created 2 years back as a outbound idoc reference to that original idoc.
And this outbound idoc is coming to XI and the same can be seen in IDX5(Table - IDXRCVPOR) for that message.
I tried to see various parameters on idoc_inbound_asynchronus FM and when I execute this FM in R/3, idocs are being created correctly and service relation ship is also correct.
I tried to debug the RFC by using dialog user in the idoc adapter - IDX_OUTBOUND_XMB. For this we forced to fail the message at the adapter level and then manually restarted in SXI_MONI so that it will stop in debug mode in IDX_OUTBOUND_XMB.. But it didn't.
Can any one help on this ?
Thanks in Advance..
Nagarjuna

If my understanding is correct, your inbound function module processing the IDoc is triggering another IDoc to be sent back to PI? If so, then have you checked the distribution model? If you want to supress it you can try removing it as the outbound Idoc for the logical system in we20 (Partner Profiles)?

How to test the sample adapter code on PI 7.1?

Hi,
I would like to test the sample adapter on PI 7.1.
I followed these explanations:
/people/gowtham.kuchipudi2/blog/2006/01/04/testing-sample-adapter
How-to deploy Sample Adapter in PI 7.1
but I still can't get things working.
The com.sap.aii.adapter.sample.ra.jar file I retrieved from the server doesn't contain any ra.xml file so I took the SampleRA.xml I found in the sample_ra.jar file fetched from a PI 7.0 server.
I used this XML file content to fill the adapter metadata in the integration repository.
The sample adapter is deployed and its JNDI name is
deployedAdapters/com.sap.aii.adapter.sample.ra/shareable/com.sap.aii.adapter.sample.ra
I don't know where to put this information in the metadata.
As a result my sender and receiver communication channels are said to be running in the runtime work bench but there is no message thrown when I put the expected file in the source directory.
The sender communication channel stays blind.
Could someone help me?
Thanks in advance for any help.
Olivier

Hi,
Thanks for your answer but there is no sample_ra.rar file on my PI 7.1 server.
Instead I have a com.sap.aii.adapter.sample.ra.jar file that is located at
D:\usr\sap\P71\DVEBMGS01\j2ee\cluster\apps\sap.com\com.sap.aii.adapter.sample.ra\connector\bin\com.sap.aii.adapter.sample.ra.rar
and
D:\usr\sap\P71\DVEBMGS01\j2ee\cluster\apps\sap.com\com.sap.aii.adapter.sample.ra\connector\connectors\com.sap.aii.adapter.sample.ra.rar
It is the same file and its content is:
testing: META-INF\                OK
testing: META-INF\MANIFEST.MF     OK
testing: com\                     OK
testing: com\sap\                 OK
testing: com\sap\aii\             OK
testing: com\sap\aii\af\          OK
testing: com\sap\aii\af\sample\   OK
testing: com\sap\aii\af\sample\adapter\   OK
testing: com\sap\aii\af\sample\adapter\ra\   OK
testing: com\sap\aii\af\sample\adapter\ra\CCIConnection.class   OK
testing: com\sap\aii\af\sample\adapter\ra\CCIConnectionFactory.class   OK
testing: com\sap\aii\af\sample\adapter\ra\CCIConnectionMetaData.class   OK
testing: com\sap\aii\af\sample\adapter\ra\CCIConnectionRequestInfo.class   OK
testing: com\sap\aii\af\sample\adapter\ra\CCIInteraction.class   OK
testing: com\sap\aii\af\sample\adapter\ra\CCIResourceAdapterMetaData.class   OK
testing: com\sap\aii\af\sample\adapter\ra\SPIConnectionManager.class   OK
testing: com\sap\aii\af\sample\adapter\ra\SPIManagedConnection.class   OK
testing: com\sap\aii\af\sample\adapter\ra\SPIManagedConnectionFactory$XIManagedConnectionFactoryController.class   OK
testing: com\sap\aii\af\sample\adapter\ra\SPIManagedConnectionFactory.class   OK
testing: com\sap\aii\af\sample\adapter\ra\SPIManagedConnectionMetaData.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIAdapterCategories.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIConfiguration.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIConnectionEventListenerManager.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIConnectionSpecImpl.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIInteractionSpecImpl.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XILocalizationUtilities.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIMessageFactoryImpl.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XIMessageRecordImpl.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XISecurityUtilities$1.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XISecurityUtilities.class   OK
testing: com\sap\aii\af\sample\adapter\ra\XITrace.class   OK
testing: com\sap\aii\af\sample\adapter\ra\package-version.properties   OK
testing: com\sap\aii\af\sample\adapter\ra\rb_JCAAdapter_ChannelMonitor.properties   OK
testing: com\sap\aii\af\sample\adapter\ra\rb_JCAAdapter_ChannelMonitor_de.properties   OK
testing: com\sap\aii\af\sample\adapter\ra\rb_JCAAdapter_ChannelMonitor_en.properties   OK
testing: com\sap\aii\af\sample\adapter\ra\rb_JCAAdapter_ChannelMonitor_fr.properties   OK
testing: com\sap\aii\af\sample\adapter\ra\rb_JCAAdapter_ChannelMonitor_ja.properties   OK
There is no ra.xml file
Regards
Olivier

How to debug Adaptive RFC

hi folks,
How to debug an adaptive RFC connection and plz leave some idea about the Bapi_Input and Bapi_output structures
thanks in advance
nikhil

Hi
If you want to debug the backend then put and external breakpoint in the abap code.
make your jco connect to a single instance
login using the user which is configured for jco.
For the front end
put a break point in your code before you call the execute method on the RFC and after it and use the debug perspective to evaluate the values.
Regards
Ayyapparaj

How to debug adapter module in PI 7.1

Hello all,
I am trying to figure out how to debug adapter module in PI 7.1.
I guess runtime debugging ( switch AS java in debug mode and attach NWDS to the AS Java to debug as module is being executed) is not possible with adapter module. Please let me know if this is indeed possible and how to enable it.
The only option is to send debug information to log file. So in the module code like:
audit.addAuditLogEntry(key, status, message);
location.debugT(SIGNATURE, message);
I've read that for PI 7.0, you need to add log-configuration.xml to meta-inf. Is this still required for PI 7.1?
My next question is how to read the log in audit log and in location. I've read that the audit log can be read in .../MessagingSystem/monitor/monitor.jsp, under which section of the page I can read the audit log? I can't see any of my log there.
For log in location, I guess I need to go to NWA, can you please share the path (navigation) in NWA to see the location?
Thanks
Jayson

> I guess runtime debugging ( switch AS java in debug mode and attach NWDS to the AS Java to debug as module is being executed) is not possible with adapter module. Please let me know if this is indeed possible and how to enable it.
It is possible for adapter modules as well. I know this from our developers
It should work like this:
/people/christian.drumm/blog/2008/09/30/debugging-java-mappings-using-sap-netweaver-developer-studio
> The only option is to send debug information to log file. So in the module code like:
> audit.addAuditLogEntry(key, status, message);
> location.debugT(SIGNATURE, message);
> My next question is how to read the log in audit log and in location. I've read that the audit log can be read in .../MessagingSystem/monitor/monitor.jsp, under which section of the page I can read the audit log?
In the RWB under Message Monitoring for Adapter, or try the shortcut
http://server:port/mdt

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to debug .sda files

Hi Guys,
Could anyone tell how to debug the .SDA files.I mean i couldn't found any option to deploy .sda files that i have built through ANT builder in NDS.Till now i am deploying it through SDM only.Is it possible to debug the .SDA files which i am deploying through SDM and debug them through NDS.
Actually i am trying to debug the Sample Adapter of SAP XI.
regards,
Gowtham K.

Hi Heiko,
>>>have you tried to start your J2EE engine in debug mode and attached to your server using the debug perspecive and JPDA?
Yes, i have started J2EE engine in debug mode and from NWDS i kept that application in debug mode.
But the problem is i am not deploying my .SDA file through NDS.I can only deploy it through SDM on J2EE server.But the same SDA file i have imported into NDS and set it to debug. But it is not getting debug. Can i deploy .SDA file through NDS.
regards,
Gowtham K.

Does anyone know how to customize a adapter (PI7.1)(not adapter module)

Dear PI experts:
i want to develop a adapter to fulfill the user' requirements,my pi version is pi7.1,and had download the sample adapter code,it's a zip file which contents some java class. and i now i have a double about developing the adapter:
1.which project type do i create for the adapter,is general java project or EJB project?
2.in the adapter project , where can i coding.
3.i don't kown what i must implement int the adapter project ,for example there may be some configuration.
do anyone had developed own adapter,could you tell me how to develop a adapter.
thaks very mutch!

Hi Kevin,
Adapter development for both PI7.0 and PI7.1 has limited resources.
You must have come across this SAP Documentation from help.sap.com:
[Adapter and Module Devlopment|http://help.sap.com/saphelp_nwpi71/helpdata/EN/8b/895e407aa4c44ce10000000a1550b0/content.htm]
This is a complete reference for understanding the Adapter framework.
Download the example Adapter from the mentioned links on the above page and try understanding and relating the java objects with the adapter frameworj and JCA.
You surely need a Java Project for the Adpater development.
You'll need to write a build file to compile it into a rar file and then toa deployable SDA. Thats the way with the example adapter.
Regards,
Alka.

Sample Adapter Migration from PI 7.0 to 7.1

Hi All,
i want to migrate the 7.0 Sample Adapter to 7.1. I followed the instructions written in the paper
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0667f56-96c7-2b10-0e9a-c40fbd523f4d
But i get the following error message in the message-monitoring, after sending a xml:
Message could not be forwarded to the JCA adapter. Reason: class com.sap.aii.af.sample.adapter.ra.XIMessageRecordImpl:sap.com/com.sap.aii.af.sample.adapter.ra @ com.sap.engine.boot.loader.ResourceMultiParentClassLoader @ 5ab9f6b4 @ alive incompatible with interface com.sap.engine.interfaces.messaging.api.Message:interface:com.sap.aii.af.ms.ifc @ com.sap.engine.boot.loader.ResourceMultiParentClassLoader @ 7d9ab9c5 @ alive
Thanks in advance
Regards Christoph

This paper is intended to show, how the sample adapter 7.1 can be used to migrate a customer adapter 7.0 to 7.1
It is not useful to help the migration of the sample adapter itself. For migration you have to compare sample adapter 7.0 and 7.1 to see the changes.
Regards
Stefan

How to use File Adapter in BPEL

Hi,
How to use File Adapter in BPEL. I am using Oracle SOA 10g. Any sample or best example in blog or elsewhere ?

Hi,
Please check the below links for samples on how to use file adapter in BPEL (in 10g/11g usage is same) and let me know any further queries.
11g - http://blogs.oracle.com/theshortenspot/entry/soa_suite_integration_part_3_l
10g - http://erpschools.com/articles/bpel-file-adapter-tutorial

How to debug module pool program

Hi everybody,
How to debug module pool program ,please send any material for module pool programming .
Thanks & Regards,
Siddivinesh.Jogu
[email protected]

Hi
Check the below link:
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
Debugging
Refer to this thread
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
Debugging
Check these documents.
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_nw04/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
ABAP Debugging
http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
Look at the SAP help link below
http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
Regards
Anji

SAMPLE ADAPTER quest

Hi
Could anyone tell me if we could deploy the sample adapter and get a complete scenario working (file to file as sender and reciever)??
I am trying to do that. I see that the adapter is able to rename my file but does nothing more than that. I dont see any messages on the communication channel too.
Could anyone give me a step by step procedure on how to get the sample adapter working as sender and reciever.
--Jai

Hi,
Related help for the Adapter Development:
Adapter Development
Adapter Development
and the error may be because of many reasons:
1) What is the status of Sender Communication Channel in the Runtime Workbench? Does it show green status?
2) Did you get messages in the SXMB_MONI?
If you get this then only you can think of getting the messages in the Receiver side.
Hope this helps,
Rgds,
Moorthy

PI7.1 Sample Adapter

I created a simple scenario utilizing sample adapter (JCA) to see how it works. It's PI7.1. The sender side works fine but i got this error message in the receiver side:
Adapter Framework caught exception: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at sample_ra, the whole lookup name is deployedAdapters/sample_ra/shareable/sample_ra.
Delivering the message to the application using connection JCA_http://sap.com/xi/XI/sample failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at sample_ra, the whole lookup name is deployedAdapters/sample_ra/shareable/sample_ra..
Can anyone please help me to solve this?
Thanks!

Check with NW Administrator how the EJB modules are named in JNDI.
Put the same name to the module parameter.
Regards
Stefan

Sample adapter Trace

Hi. Can anyone tell me how to view the Trace or log file for the sample adapter (sample_ra.sda). I would like to know the location to which the trace is written out and also the severity level.
--Jai

Hi,
a) In order to trace the message you have go to runtime workbench
b) Select message monitoring
c) Select message press detail display where in you can see and trace ur message
Regards,
G.Varun Kumar

How to Debug Sample Adapter

Similar Messages

Maybe you are looking for