CTS+ PI Export fails: Error retrieving JCO destination

[Former Member]

I'm setting up CTS+ for my PI landscape. I'm following the instructions in "Best Practices for Implementing CTS+" (April 2008) and "How Tou2026 Configure Enhanced CTS for SAP NetWeaver Exchange Infrastructure 7.0 SPS14" (March 2008).

Things were going well until I tried to export an object. At that point I was prompted to choose an export method and chose "Transport using CTS". This leads to the select objects step which completes successfully.

In the next step (Select Transport Request), however, I stop with an error saying "Error retrieving JCO destination". The log starts out:

====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.misc.api.ResourceException: Error retrieving JCO destination
	at com.sap.aii.ib.server.transport.impl.cts.SyncCtsWrapper.getTransportRequest(SyncCtsWrapper.java:127)
	at com.sap.aii.ib.server.transport.impl.cts.SyncCtsWrapper.getCtsTransportRequests(SyncCtsWrapper.java:51)
	at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.getCtsTransportRequests(TransportServiceImpl.java:602)
	at com.sap.aii.ib.server.transport.TransportServiceBean.getCtsTransportRequests(TransportServiceBean.java:113)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)

then continues

Serialized cause: com.sap.tc.di.draft.ts.TsConfigurationException: Error retrieving JCO destination
	at com.sap.tc.di.draft.cts.impl.adapters.jco.JCoAdapter.initializeJCo(JCoAdapter.java:69)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.JCoAdapter.<init>(JCoAdapter.java:44)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsJCoAdapterNew.<init>(TmsJCoAdapterNew.java:73)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsFactory.createTmsAdapter(TmsFactory.java:37)
	at com.sap.tc.di.draft.cts.impl.adapters.jco.TmsCommonProvider.createConfiguration(TmsCommonProvider.java:22)
	at com.sap.tc.di.draft.config.ts.RegistrationFactoryImpl.createConfig(RegistrationFactoryImpl.java:56)
	at com.sap.tc.di.draft.ts.impl.TransportManagerImpl.getConfig(TransportManagerImpl.java:96)
	at com.sap.tc.di.draft.ts.impl.TransportManagerImpl.getMyDefaultRequest(TransportManagerImpl.java:70)
	at com.sap.aii.ib.server.transport.impl.cts.SyncCtsWrapper.getTransportRequest(SyncCtsWrapper.java:124)

There's nothing here which tells me which JCO destination is missing or misconfigured.

I have configured the CTSserver destination in my dev system's NWA and, for testing purposes, have tested that it connects with my userid and password. (Once I know that this works I'll change that to SSO with SAP logon tickets.)

How do I debug this?

How do I identify the missing or broken JCO destination?

[paul_power]

Hello Murray,

What are the results of the transport checks:

STMS=>overview=>system=><sid>=>transport tool=>check

etc

Is their a transport path set up with the sids being used here?

regards,

Paul

[Former Member]

Hi Paul

The tp config for the PI landscape is fine. We've been using it for ABAP-stack transports for the past year or so. I have run your suggested check as well just to be sure and everything comes back "green".

The problem is on the Java side, not the ABAP side.

I am trying to use the export function from the PI Enterprise Services Builder. The test steps are described in the documentation listed above. I'm trying to "Export Design Objects" which is a four step wizard - Select Source, Select Objects, Select Transport Request then Preview/Analysis. This wizard offers the choice of exporting via the filesystem or a CTS request. If the development system has not been configured as a CTS+ enabled source system, the CTS option is not available - I get the option so I'm guessing I've done the configuration part correctly "inside" PI.

What should happen is that the CTS+ connection should use the associated ABAP client to create a transport request and then link the exported objects to that transport request. The QA system needs to be configured, then, to recognise these objects and understand how to deploy them. At the moment I can't get past step 1.

[Former Member]

Refer to SAP Note 1155884 for troubleshooting steps and notes.

This note summarises a series of steps and checks which will either solve the problem or gather analytic information required before logging a support call. Following these steps I discovered a spelling error in the name of the CTSserver JCO destination.

The mispelled destination was connecting fine and this threw me off the track. The fact that the export tool didn't say what JCO destination it was unable to find left me assuming that I was looking for something other than the destination I had set up and successfully tested.

The destination name needs to be specified, in NWA, as "sap.com/com.sap.tc.di.CTSserver". I had initially thought that the sap.com prefix was assumed and then I mistyped it when I decided it needed to be stated explicitly. Note also that the "s" for server must be in lower case - s not S - which apparently contradicts some releases of the installation documentation.