Production processes imported from another server are not executed on the new PAM server.
The processes were created in PAM 4.2 SP2 and integrated with SDM 12.9. The new servers have PAM 4.3 SP3 and SDM 17.1.
The client uses in particular an operator that comes after installing the CA Service Manager connector. The operator is called "Select object" to obtain the data of a ticket. However, after logging in correctly and moving to this object, an error occurs and it does not progress anymore. The messages of the log that appear are:
2018-10-09 19:48:20,114 ERROR [com.optinuity.c2o.service.serviceoperation.ServiceGroupXmlImpl] [.17.0.49-8443-6] Could not find resource bundle for the service group Default.CASDServices.Name
2018-10-09 19:48:20,129 ERROR [com.optinuity.c2o.service.serviceoperation.ServiceGroupXmlImpl] [.17.0.49-8443-6] Could not find resource bundle for the service group Default.CASDServices.Name
2018-10-09 19:56:36,306 ERROR [com.optinuity.c2o.util.JMSMessagePublisher] [ool-17-thread-1] Looking up QueueConnection Factory
2018-10-09 19:56:37,397 ERROR [com.optinuity.c2o.util.JMSMessagePublisher] [43-5fae2093fc53] Looking up QueueConnection Factory
2018-10-09 19:56:39,532 ERROR [com.optinuity.c2o.service.serviceoperation.casdserviceoperation.CASDWrapper] [ef-ae1c6fadba94] Fault returned by the WebService:
soapenv:Client
Error fetching: AHD03053:Cláusula Where incorrecta: Parse error at : "cr:684386" (syntax error)
Error fetching: AHD03053:Cláusula Where incorrecta: Parse error at : "cr:684386" (syntax error)
103
2018-10-09 19:56:39,533 ERROR [com.optinuity.c2o.service.serviceoperation.casdserviceoperation.RunnerSDSelectDataServiceOperation] [ef-ae1c6fadba94] com.optinuity.c2o.util.C2OException: Service Operation succeeded. Fault returned.
2018-10-09 19:56:39,533 ERROR [com.optinuity.c2o.service.serviceoperation.casdserviceoperation.RunnerSDSelectDataServiceOperation] [ef-ae1c6fadba94] SelectDataServiceOperation failed to execute:
com.optinuity.c2o.util.C2OException: Service Operation succeeded. Fault returned.
Could it be that the object "Select object" can no longer be used with SDM 17.1? I read in other similar cases, which recommend using the Standard SOAP Operator and calling the doSelect method. However, for me it would be faster to just adjust this operator since the client uses a lot of its custom processes. In addition, the customer needs to upgrade to production CA SDM 12.9 to 17.1 but if their flows do not work or delay in redoing them, it would not be convenient, so they would expect the least possible change in their flows.
I would greatly appreciate your prompt response and support. If they require more data or a small flow, I upload it.
Thak's!
Crristian.