Hi people I reply back with the final result.
I indicated the correct instruction in a filter, in a Run Process Action: java -Dentorno=D remedyServer.Access new $field1$ password $field2$ $field3$ "$field4$" "$Description$" $field5$ $field6$ "$field7$" J "$field8$" "$Field9$" "$Field10$" It did not return an error, but the api did not do what it had to do. But if instead of launching it from a filter it was launched from an active link, the api worked correctly. So, I performed the actions to launch the filter in a Remedy User client in the server's computer, and surprisingly the api worked. From that moment, the api worked from any computer. It seems as the action of launching the filter in the server's computer unblocked the api. In fact I have no logical explanation for this. May be some of you have had an experiencie like this. Anyway the problem has been resolved. Thanks & regards, Sergio Tomillero -- View this message in context: http://www.nabble.com/Problems-calling-java-api-from-filter.-tp20086003p20205056.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
