No Access to Adapter Monitor /

[Former Member]

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

[Former Member · Accepted solution]

Kostyra,

Adapter monitoring is changed recently in the newer versions. Earlier if you want to see any erros for any communicaton channel we used to go to adapter monitoring and from there we will go.

But now you have to go to communication channel monitoring and then click on the adapter type or give your communication channel name and click on Use Filter. It displays your communication channel.

Hope this is what you are looking for?

---Satish

[Former Member · Accepted solution]

Hello Satish,

The XI ask, if the SLD is reachable, if the integration Engine knows the business system and if the roles in the sxms_conf_items and SLD are consistent. The Proxy Runtime shows an error (red dot).

One of our developers asked me, if the RFC Adapter can work with a 4.6c System??

Does anyone anything about this??

@Bhavesh:

We get this message "parameter JCO.Request and JCO.Response where <null> (server: RfcServer[RFC_NEU]1)" when we run the program on the R/3 4.6c system.

Thx Philipp

[bhavesh_kantilal · Accepted solution]

RFC adapter supports the 4.6 R3 system. No issue on that front.

1. Make sure that the Prgram ID in the TCP IP connection and the Sender RFC adapter are the same.

2. Make sure that the SAP Gateway Host and service in the TCP IP Connection are those oof your R3 system

3. Make sure that in the Sender RFC adapter, the option Advanced Mode is selected and the option Verify Sender System is deslected under the advanced mode.

4. Look into Comm Channel Monitoring in RWB and let us know what the error is.

Regards

Bhavesh

[Former Member · Accepted solution]

Hello Bhavesh,

we already processed the first 3 steps you described. We only cannot take a look in the Adapter Monitor of the RWB.

I checked the runtime workbench the following points:

Integration Server

Integration Engine ZXI shows yellow

Business Process Engine ZXI shows green

Mapping Runtime shows green

Adapter Engine shows green

Integration Engines

Proxy Runtime SID shows red

Tools:

System Landscape Directory shows green

Integration Directory shows green

Integration Repository shows green

Runtime Workbench shows green

We don't have any idea where reason of the problem is?

We are happy about every answer!!

Best Regards Philipp

[Former Member · Accepted solution]

Hello Experts again,

we just found out the FQDN wasn't right in the XI. The Adapter Monitor shows that the User and Password of the RFC Connection weren't right.

The English Part of the message was:

com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE:

So we keep on trying.

Thx so far! Please keep on supporting!

Best Regards

Philipp

[bhavesh_kantilal]

>

> 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?

How did you do this? Where are you getting this error? Is it in the Receiver RFC >.

>I reward every answer!!

If i were you I would never do that. The Rules of Engagement encourage points for helpful answers and not every answer

Regards

Bhavesh

[Former Member]

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 XI’s 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”.

• &#61472;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 XI’s 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.

• &#61472;Double-click on the business system in the Integration Directory.

• &#61472;Switch to Edit mode.

• &#61472;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.

• &#61472;The RFC Destination is from step 3.1.

• &#61472;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

[Former Member]

Hello Hemant,

we don't want to use the IDoc Adapter, we want to use the RFC Adapter. Do you know what we have to do in this case??

Best Regards

Philipp

[Former Member]

Kostyra,

Have you checked your communication channel as I mentioned earlier? Do you see any errors in it?

---Satish

[Former Member]

Hello Satish,

we have only an Adapter Monitor (must be the old version). But the Adapter Monitor can be displayed. The site is not shown in the browser.

So we can get any information out of the monitor. Any other hints?