Symptoms

Additional K2Connect Service Instance
 

Diagnoses

We have a requirement to call BAPI's against different SAP systems. As per page 23 of 300.PEK K2 connect configuration and administration, I have manually created a new service instance "'Company name' DSM" pointing to the SAP DSM system.

In K2 Service Object Designer I have set this new destination as the default and created a new Service Object "Test". I was able to succesfully pubish this service object, however it did not publish to the new service instance. Additionally all of the existing service objects in the original service instance are now copied in the new service instance.

How do we go about publishing service objects to the new service instance?
 

Resolution


You still need to manually refresh the manual service instance. When you publish from VS or refresh from Admin tool it only refreshes the default instance. We will be changing this in future