Adapter Monitoring - Post Transportation

Hi Forum,
We have an external adapter (Siebel-HTTP Protocal) in our Dev environment and we used to monitor under Adapter Monitoring. We are in the process of QA, and successfully transported and during testing, i am unable to monitor the said adapter.
Any Inputs, where to find and how to resolve this problem?
Your help is highly appreciated.
Thanks & Regards

Hi,
I have checked and compared Visual Administrator and found the Siebel Adapter is not displaying under the Deployed Components. If anybody is having a good document on how to deploy, plz do forward to my mail id [email protected] or provide me link.
Thanks & Regards

Similar Messages

DB Adapter and jca transport: monitoring and management

Greetings.
We have faced with several issues with DB Adapter and JCA transport proxy. We use pooling DB adapter. As the result - the pooling stop. I would like to know:
1. Is the way to monitor pooling threads of DB Adapter in OSB? I would like to answer the question "does it work?".
2. Is the way to restart pooling in JCA Proxy service? The way we found is re-save OSB configuration in OSB Console, bu it is terrible.
I use:
                    ActivationSpec="oracle.tip.adapter.db.DBActivationSpec"
                    DescriptorName="DescriptorName"
                    QueryName="QueryName"
PollingStrategyName="LogicalDeletePollingStrategy"
                    MarkReadFieldName="IsLoad" MarkReadValue="Y"
                    MarkReservedValue="R${IP[-3]}" MarkUnreadValue="N"
                    SequencingFieldName="ID" MaxRaiseSize="5"
                    MaxTransactionSize="unlimited" PollingInterval="180"
                    NumberOfThreads="1" UseBatchDestroy="false"
                    ReturnSingleResultSet="true"
                    MappingsMetaDataURL="MappingsMetaDataURL.xml" />
Oracle Service Bus Version: [WebLogic Oracle Service Bus 10.3]
Regards,
Boris
Edited by: Boris Ilyushonak on 14-Mar-2011 05:22

1. Is the way to monitor pooling threads of DB Adapter in OSB? I would like to answer the question "does it work?". OSB provides OOB support for monitoring -
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/consolehelp/monitoring.html#wp1008658
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/index.html
2. Is the way to restart pooling in JCA Proxy service? The way we found is re-save OSB configuration in OSB Console, bu it is terrible.You may restart/redeploy DBAdapter in Weblogic Admin Console and polling should start. Ideally poller transports does not stop polling. Let us know the complete detail if you experienced such issue.
Regards,
Anuj

Adapter Monitoring with CCMS

Hi,
is there anybody who already set up an adapter monitoring with CCMS using the alert framework of Runtime Workbench ?
Background:
When using the existing MTE's in CCMS (J2EE Monitor Templates - All Systems - <SID> - J2EE Applications - SAP XI Adapter Engine) only rare monitoring information related to XI messages are posted.
What I would like to see are information about the adapters provided in the logfiles of each adapter.
For example as soon there's a permission problem for a directory in File Adapter an alert in CCMS should be raised.
I already checked SAP notes 870232, 913858 and 824039.
Any feedback appreciated.
Cheers,
Juergen

Hi,
You can configure the CCMS as per the following two blogs,
Part 1: /people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i
Part 2: /people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii
Configure the Alert Framework with the below Blog as reference,
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
Then forward the Alerts created in the CCMS to Alert Frame work, the required steps are given in the below help links.
http://help.sap.com/saphelp_nw04/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/30/62e77b2f4865488a866d4103923a93/frameset.htm
Then any alerts that gets generated in CCMS can be passed to the Alert Category kept configured in the Alert Framework.
Hope this helps you

Issue with AS2 Adapter monitoring

Hi All,
I am using Seeburger AS2 Adapter in our XI project we are able to post and retrieve
messages through AS2 communication,but we are facing the problem of monitoring the messages if any incoming messages failed in the AS2 adapter only due to some network failure or some other issue we are not able to track which message is failed and what payload it contains as in Adapter Monitoring or communication channel monitoring AS2 Adapter shows the only "Failed Session"
Do we have any application to monitor it in XI.
Regards
Gaurav

Hi Gaurav,
Have you tried Tcode SXMB_MONI . In this by giving some details about your scenario, it will give you the information about all the messages which are successful or not. Here you can see the payload af successful messages and error in failed message by clicking on the perticular message.
hope this will help.
regards
HONEY

Cannot display Adapter Service in Adapter Monitor - XI Runtime Workbench

Dear Experts,
I have already done the system copy XI 3.0 from Win Server 2003 32bit to WIn Server 2003 64bit.
I have also done the post activities in NW AS ABAP system copy and NW AS JAVA system copy.
I have a problem now,
I cannot display the adapter service in SAP XI Runtime Workbench ( http://jktbtr-sap01:50000/rwb/index.jsp )
Tree Domain -> Integration Server -> Adapter Engine jktbtr-sap01
Button Adapter Monitoring.
In the previous source system I can see all the adapter service : BC, File, JDBC, JMS, JPR, Mail , RFC, SOAP, XI.
But in the target system, I just found JPR with red light.
What configuration should I set to register and start those adapter services in target system?
Regards,
Adhi

can u check whether u are able to see the list of adapters in communication channel. when u select the adapters.
also do the CPACACHE refresh.
chirag

Link to Communication Channel and Adapter Monitoring not opening

Hello All,
we are on PI 7.0. In teh RWB, we are not able to see the Communication Channnel Monitoring as well the Adapter Monitoring It is giving Page cannot be Displayed.
please tell us the way ahead.
Regards
Chakra and Somnath

Hi Somnath,
when the error occurs check the url of the page that cannot be displayed and verify if the hostname is correct.
It could be a problem of not right setting in exchange profile.
Also verify that you have enough authorization, trying to logon with PISUPER user if you can.
Hope it helps,
Regards,
Sergio

Error while opening Adapter Monitoring in Runtime Workbench

Hi,
I am unable to open Adapter Monitoring from
Runtime Workbench -> Component Monitoring -> Adapter Monitoring
When I tried to open, I am getting following message in the new window:
"The page cannot be displayed"
Please let me know where I can enable this option.
Thanks,
Yogi.

Hi,
Go thru this SAP Note- 768456,928862
Also this doc may help u-https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
Regards,
Moorthy

File Adapter or File Transport which one will give more performance

Hi all,
File Adapter or File Transport which one will give more performance ? in OSB?
Which one to select any one did performance analysis?
Thanks
Phani

Why don't you just go read some benchmarks?
http://www.barefeats.com/mbpp18.html

Error in File Adapter Monitoring

Hi,
I have created a Sender Communication Channel to pick the file:
The following error message is being displayed in Adapter Monitoring:
Sender Adapter v2622 for Party '', Service 'BS_TRD_PILOT_YOGS':
Configured at 2006-12-19 05:52:17 UTC
History:
- 2006-12-19 05:56:01 UTC: Retry interval started. Length: 60.000 s
- 2006-12-19 05:56:01 UTC: Error: Conversion of complete file content of 'OB10_input.xml' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 14: missing structure(s) before type 'E1EDK14'
- 2006-12-19 05:56:00 UTC: Processing started
- 2006-12-19 05:55:01 UTC: Error: Conversion of complete file content of 'OB10_input.xml' to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 14: missing structure(s) before type 'E1EDK14'
- 2006-12-19 05:55:00 UTC: Processing started
Please anybody do the needful.
Thanks,
Yogi.

Hi Yogi,
Just go thru your source structure once again.Such type of errors usally come when your source structure is not proper adn also when the parameters for comm'n channel are not mentioned properly.
Usually the Content Conversion Parameters(recordset structure and recordset sequence fileds).
regards
Madhu

Mail Adapter Error occured in Adapter Monitoring....

Hi
I have done the Mail>XI>File senario.... the xi server is sometimes its picking up the mails but some times its not picking... i have give trasport protocol as IMAP4 and url as pop://ipaddress.... I have created the asyncronus message types...n i have given the quality service as Exactly Once... when ever the server is picking file from mail inbox its sending file to the destination directory successfully but in destination side i am getting only the complex tags like the following
<?xml version="1.0" encoding="UTF-8"?>
<ns0:File_Message_Type xmlns:ns0="http://mailtofiledemo.com/ravi"></ns0:File_Message_Type>
i am not getting any nodes inside those tags.... In adapter monitoring i am getting the following error:
error occured: [2006-06-05T05:44:06Z] 0 new messages found; no action takenexception caught during processing mail message; com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
I am using SquirrelMail(webmail) server... so please help me...
I have tried with pop3 alos but its not working
Thanks & Regards
Ravi Shankar B
Message was edited by: RaviShankar B

Hi,
Try giving POP3.
and correct address.. pop3://etc... Remember to give the name of the folder from where the message have to be picked.
Regards
Suraj
Message was edited by: S.R.Suraj

Error in Mail Adapter Monitor......

Hi....
I have done the mail adapter and i got following error in Adapter Monitor(Mail Adapter)
error occured: [2006-05-31T05:53:34Z] 0 new messages found; no action takenexception caught during processing mail message; com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
how to recover this....
I am using pop3 mail server
Thanks & regards
Ravi Shankar B

hi,
check if you don't have quality of service Best Effort - BE in your mail sender channel
if so change it to EO - Exactly Once
and activate and your channel once more
this setting will eliminate:
NO_RECEIVER_CASE_BE error
change this setting and let me know if it worked
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Sender ADapter Monitor- ArrayIndexOutOfBOunds Exception

Hi
As me subject line reads, I am getting an "ArrayIndeXOutofBOunds 9" exception at the sender adapter monitor logs in the RWB.
I have an adapter monitor module that picks up the file from the source and pushes the file to a target directory based on some condition. I am able to see the file being pushed to the target directory but not able to view the "pipeline steps" in the message monitor.
Do you think a restart of the server might fix the issue/ do you think there is a problem in my code. I have used just one array and i have checked that array if it is being accessed out of its bounds?
Thanks
krishna

Hi,
>>>>>ArrayIndeXOutofBOunds 9"
looks like an error in code
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

No Access to Adapter Monitor /

Hello Experts,
everytime i try to take a look on the Adapter Monitor, the page in the ie is not able to be shown. Does anyone know the reason for this ?
We connect our xi to a R/3 4.6c system and when we call the xi from the r/3 we get the following message: "parameter JCO.Request and JCO.Response where <null> (server: RfcServer[RFC_NEU]1)". Do you have any hints?
We already checked that the SAP XI Adapter:RFC is running.
I reward every answer!!
Thx and best regards Phil

Hi,
Ithink u just check the Logical System name and the RFC connection with the XI.
Take the following step:
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.
Regards
Hemant
Reward points if find helpful

Adapter Monitor Error and SQLServer JDBC Test

Hello !
I have a problem with communication in scenario RFC>XIJDBC !
How i can test my JDBC Coonnection ...database is SQL Server !
In Adapter Monitor i have two errors:
1 - JDBC Error:
Receiver Adapter v2112 for Party '', Service 'BS_IBATCH':
Configured at 2006-06-01 14:45:27 BRT
History:
- 2006-06-06 16:08:47 BRT: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
- 2006-06-06 16:08:47 BRT: Processing started
- 2006-06-06 16:03:46 BRT: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
- 2006-06-06 16:03:46 BRT: Processing started
- 2006-06-06 15:58:46 BRT: Error: TransformException error in xml processor class: Error processing request in sax parser: No 'action' attribute found in XML document (attribute "action" missing or wrong XML structure)
2 - JPR Error:
Error getting JPR configuration from SLD. Exception: No entity of class SAP_BusinessSystem for NWD.SystemHome.euro11 found
No access to get JPR configuration
Someone can help mme in this question?
Regards.
MBoni

Hi,
The JDBC adapter error looks like- your xml document is not correct. ie. the structure which is given to JDBC adapter.
Have a look into this-
http://help.sap.com/saphelp_nw2004s/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
Also look into this-for structure
/people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
Regards
Moorthy

More fields in XML structure error in Adapter Monitor

Hi all
I am getting the following error in the adapter monitor
Error: Message processing failed: Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value ' ')', probably configuration error in file adapter (XML parser error)'
I am using FCC in the rx adapter. I have also checked the fields for any extra fields but there isnt any.
kindly suggest what could be throwing the error
regards
krishna

Hi raj
here are the CC parameters.
BEGIN.addHeaderLine     0
BEGIN.fieldFixedLengths     2,1,3,2,4,1,8,12,8,2,307,12,8,12,18
BEGIN.fixedLengthTooShortHandling     Ignore
BEGIN.endSeparator     '0x0D''0x0A'
CLIENT_RECORD.addHeaderLine     0
CLIENT_RECORD.fieldFixedLengths     2,12,9,4,15,15,4,20,12,9,8,1,1,25,10,1,25,10,1,6,1,1,1,1,1,10,8,1,25,2,1,1,1,106,12,38
CLIENT_RECORD.fixedLengthTooShortHandling     Ignore
CLIENT_RECORD.endSeparator     '0x0D''0x0A'
RELATION_RECORD.addHeaderLine     0
RELATION_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,9,8,1,25,10,1,25,10,1,6,1,1,181,12,38
RELATION_RECORD.fixedLengthTooShortHandling     Ignore
RELATION_RECORD.endSeparator     '0x0D''0x0A'
ADDRESS_RECORD.addHeaderLine     0
ADDRESS_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,5,6,8,24,24,2,35,15,4,15,4,70,8,8,1,50,12,38
ADDRESS_RECORD.fixedLengthTooShortHandling     Ignore
ADDRESS_RECORD.endSeparator     '0x0D''0x0A'
GIVING_REC.addHeaderLine     0
GIVING_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,1,1,1,1,1,1,1,1,1,1,281,12,38
GIVING_REC.fixedLengthTooShortHandling     Ignore
GIVING_REC.endSeparator     '0x0D''0x0A'
ZIKT_REC.addHeaderLine     0
ZIKT_REC.fieldFixedLengths     2,12,9,4,20,9,2,3,2,8,1,1,277,12,38
ZIKT_REC.fixedLengthTooShortHandling     Ignore
ZIKT_REC.endSeparator     '0x0D''0x0A'
BEPER_REC.addHeaderLine     0
BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,291,12,38
BEPER_REC.fixedLengthTooShortHandling     Cut
BEPER_REC.endSeparator     '0x0D''0x0A'
SCORE_BEPER_REC.addHeaderLine     0
SCORE_BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,3,4,1,1,284,12,38
SCORE_BEPER_REC.fixedLengthTooShortHandling     Ignore
SCORE_BEPER_REC.endSeparator     '0x0D''0x0A'
INDBES_REC.addHeaderLine     0
INDBES_REC.fieldFixedLengths     2,12,9,4,20,9,9,2,2,8,8,8,1,256,12,38
INDBES_REC.fixedLengthTooShortHandling     Ignore
INDBES_REC.endSeparator     '0x0D''0x0A'
FUNCTIONAL_REC.addHeaderLine     0
FUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,8,8,1,4,2,2,1,1,1,1,8,1,1,233,12,38
FUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
FUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ACT_REC.addHeaderLine     0
ACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,3,5,1,263,12,38
ACT_REC.fixedLengthTooShortHandling     Ignore
ACT_REC.endSeparator     '0x0D''0x0A'
SCORE_REC.addHeaderLine     0
SCORE_REC.fieldFixedLengths     2,12,9,4,20,9,3,4,1,1,285,12,38
SCORE_REC.fixedLengthTooShortHandling     Ignore
SCORE_REC.endSeparator     '0x0D''0x0A'
ZFUNCTIONAL_REC.addHeaderLine     0
ZFUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,12,3,2,8,8,5,1,8,8,8,4,2,2,1,1,1,1,210,12,38
ZFUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
ZFUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ZACT_REC.addHeaderLine     0
ZACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,3,5,8,8,5,8,1,242,12,38
ZACT_REC.fixedLengthTooShortHandling     Ignore
ZACT_REC.endSeparator     '0x0D''0x0A'
COMMENT.addHeaderLine     0
COMMENT.fieldFixedLengths     2,12,4,140,1,191,12,38
COMMENT.fixedLengthTooShortHandling     Ignore
COMMENT.endSeparator     '0x0D''0x0A'
END_REC.addHeaderLine     0
END_REC.fieldFixedLengths     2,6,6,6,6,6,6,6,6,6,6,6,6,6,6,6,1,257,50
END_REC.fixedLengthTooShortHandling     Ignore
END_REC.endSeparator     '0x0D''0x0A'
REgards
krishna

Adapter Monitoring - Post Transportation

Similar Messages

Maybe you are looking for