1. User Guide
  2. Toolbox
  3. System Setup
  4. Configuring Outbound Systems
  5. Outbound System Types and Respective Configurations
  6. CRM Legacy for OXI Profile Lookup/Download

CRM Legacy for OXI Profile Lookup/Download

Outbound Type CRM_LEGACY is used when integrating with OPERA Room Reservations Cloud Service for Profile Lookup and Download and OPERA Customer Loyalty Tracking Cloud Service for membership and award management; along with other legacy OXI integrations.

  1. Outbound Code can be created at the Global (Chain) or Property level context based on the CRM system integration requirement.

    Note:

    It is recommended that you create outbound codes at the Global level if all the properties in the chain use the same external system.

  2. Select Outbound Type CRM_LEGACY.

  3. Enter a unique outbound code, for example: CRMORSCHAIN1.

  4. Enter a description for the CRM Legacy System summary.

  5. Protocol is defaulted with XML for CRM_LEGACY integration.

  6. Select the Authorization Type for CRM Legacy integration:

    1. Select NONE for Non-SSD OPERA V5 ORS.

    2. Select BASIC for SSD OPERA V5 ORS.

  7. Enter the Application Key. You must obtain the value from 05 ORS Setup > External Database > Local JNDI. Skip for non-O5-ORS applications.

  8. Add a new row, select GetExternalProfiles, and enter the service path to fetch profiles. Configure https://{host}/...

    1. Configure https://{host}/Operajserv/OperaWebSvcs/Lookup for O5 ORS application lookup.

    2. Configure https://{host}/Operajserv/OXIServlets/ORSLookup for non-ORS application lookup using OXI XML specifications(plquery & plresult).

  9. Add a new row, select DownloadExternalProfile, and enter the service path to download profiles, for example: https://host/Operajserv/OXIServlets/ORSLookup.

  10. Add New row, select GetMembershipDetails, enter service path for get membership details of the profile, for example: https://host/Operajserv/OperaWebSvcs/MemberInfo.

  11. Add New row, select PostMembershipNumber, enter service path for download profiles, for example: https://host/Operajserv/OperaWebSvcs/NewMemberCard.

  12. Add New row, select RedeemAward, enter service path for download profiles, for example: https://host/Operajserv/OXIServlets/ORSLookup.

  13. Save the Outbound Code configuration.

  14. If an existing OXI external system (for example ORS) is used for Profile Lookup and Download, ensure the Lookup check box is selected for the External System.. See Configuring External Systems.

  15. Associate the Outbound code with the External Database code of the OXI Interface. See Configuring External Databases.

  16. Define Interface Mappings for Profile Types group for the OXI Interface. See Configuring Interface Mapping.

  17. If you are trying to configure an OXI interface for the first time:

    1. Refer Exchange Interface Setup. See Interface Setup.

Parent topic: Outbound System Types and Respective Configurations