Hello all, I’m hoping someone here will be able to help me out. Recently my team has been working on upgrading our instances of IdentityIQ from 7.1 to 8.2. Through the upgrade process we were able to get to 8.1 but going from 8.1 to 8.2 we are facing an issue when building our war file through SSB.
In a Java class we are using a set of classes in the sailpoint.connector.salesforce.webservices.partner package to make Soap calls to salesforce. We found out that these files from the sailpoint.connector.salesforce.webservices.partner package are within the connector-bundle.jar in IIQ 8.1. When we go to do a IdentityIQ 8.2 build it fails because it can no longer find the files that were in the sailpoint.connector.salesforce.webservices.partner package. When we exploded a base 8.2 war file we could not find the connector-bundle.jar anywhere.
Does anyone know what happened to this package? Was the package moved to a different jar or did they get rid of this package and it’s classes all together? If they did get rid of these classes, what is the new way to make soap calls to Salesforce?
From 8.1p2, 8.2 and 8.0p4 onwards, the SalesForce Connector no longer uses or supports webservices partner stubs i.e., sailpoint.connector.salesforce.webservices.partner classes. You can see this in the 8.2 release notes:
CONJUBILEE-597: The Salesforce Connector will not support out of the box salesforce partner stubs.
@paulo_urcid oh wow, well that explains that. So if all of that is removed, how does one go about doing what they were doing with the webservices partner stubs? like what do I use in place of the webservices partner stubs. I wasn’t able to find any documentation on that. Some of the stuff that we are using the webservices partner stubs for is the execute a salesforce query to get specific data or update various salesforce objects.
If you need to make additional WebService calls to SalesForce, consider using standard Java or other 3rd party libraries. There is no additional information in the SalesForce Connector guide regarding a workaround to this.