Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

These instructions outline the process from switching from RTPConnect to Unity for Order Processing. Every Aspenware Commerce customer uses Unity but not all use Unity for Order Processing. RTPConnect is RTP’s API.

Instructions

  1. Update Rental Locations/Distributor Code field in Aspenware Admin to be RTP Sale Location Codes rather than RTPConnect Distributor Codes.

  2. Verify all settings in Unity rtp-confing.json file. Some settings in this file are not used when using RTPConnect as the OrderProcessor so verify all settings are correct before changing the setting in #3 below. Review all settings but these are the ones to be sure are set correctly because these are not used when using RTPConnect as the Order Processor.

    1. "PaymentMethodCodeOrder": 1,
"PaymentMethodCodeFulfillment": 9999,

  3. Update Unity rtp-config-json setting, "OrderProcessor" to the value, “Base” rather than “Connect”.

  4. Recycle the IIS application pool being used by Unity.

  5. Smoke test site after this change.

 

  • No labels