Hi,

is anyone out there using the wM Remedy Adapter 6.0 and is willing to share his experiences with us?

For the start here are my first experiences (most of them ended up as a Feature Request for future versions):

• Setting the Port is currently not possible in connection config screen
  Set the Environment Variable ARTCPPORT instead (not valuable in all cases)
  or use RPC-Mode for the connection which impacts performance on AR Server
  Side → Feature Request
• DataType Attachment/Attachment Pool not supoorted → Feature Request
• There is currently no support for Polling/Listening Notifications like JDBC, JMS,
  MQ, … are providing. → Feature Request

On the other side the form reports missing inputs for required fields without defaults. But I am sure that I have entered them in the inputs for the adapter service. → Service Request is currently under investigation.

Regards,
Holger

Hi,

I am sorry for the delay, but it took some month to get some of the issues mentioned above to be fixes. Meanwhile new issues havae came up, so I want to update this thread:

The fixed issues can be found in RMDY_6-0_Fix2, as there are:

• Ports can be set via the connection config no matter of Remedy API or
  Remedy Server Version.
• Missing Inputs are also fixed now.
• Remedy 7 should be supported according the Readme for Fix2.

Still open are the following issues:

• Support for DataType Attachment/AttachmentPool
• Adapter Service Template for GetMultipleEntries (can be worked around with
  a Find and Looping over the result to Get the Entries one by one)
• Polling and/or Listening Notifications (we are currently using JDBC Notifications
  as a workaround for this, as the provided Notifications (Email/WebService) will
  require additional coding at our partners side).
• …

Please feel free to update this thread with your own experiences and/or encounterings with this Adapter.

Regards,
Holger

Hi,