Accelerator Setup

1. Create the ATP database schema with the name 'HGBUDBCS' and with the following grants: Connect, Resource, Create Job, Create Sequence, Create Table, Create Procedure, and Create View.
2. Run the Accelerator ATP script, the Target External System ATP script, and the Drop DB Objects script.
3. Use one of the following methods to add configurations for the Target External Systems:
   1. Run the below SQL Query and replace the highlighted bind variables with the appropriate values. Other configuration values are selected from the "GLOBAL' record (having default pre-seeded data).

      insert into OHIP_OIC_EXT_SYS_CONFIG_TAB (select err_status, parking_time, logging_enabled, systimestamp, systimestamp, call_parent_int, :CUSTOM_EXTERNAL_SYSTEM_ID, max_num_records, purge_freq, :[e-mail], :CUSTOM_EXTERNAL_SYSTEM_ENDPOINT from OHIP_OIC_EXT_SYS_CONFIG_TAB where external_system_id = 'GLOBAL'); commit;

   2. Alternately, after the Listener integration is activated for a particular external system, the 'GLOBAL' record data is automatically cloned for the external system. Add (that is, update) the target external system integration endpoint details and update the other configuration settings if required in this configuration table.
4. Update the Global support email in the ATP instance by executing the following SQL query after replacing the highlighted text with the desired global support email Id:
   1. update ohip_oic_ext_sys_config_tab set err_email = :YOUR_DEFAULT_SUPPORT_EMAIL_ID where external_system_id = 'GLOBAL';            commit;
5. Import the Accelerator Package and Recipe (that is, starter kit) into your OIC instance under Packages.
6. Set up the following connections in the OIC instance:
   1. Oracle Hospitality Connection for Hospitality Adapter
   2. Oracle ATP Connection for ATP. For the service name, unzip the wallet file, open the tnsnames.ora file, and pick one of the service names.
   3. Oracle REST Connection for REST Integration Trigger
   4. Oracle Hospitality File Server Connection to secure the Business Event payload in case the ATP database is down. While configuring the FTP, the error message includes the following information if the security policy was changed: "CASDK-0004: Failed to authenticate against the application with the credentials provided."
7. In OIC, configure the value for GLOBAL_Notification_Email in the Lookup Table ORACLE-BRT_Hospitality_Resequencer_Lookup. This global email Id is used to send email in case the ATP is down or not reachable.
8. Activate all integrations in the accelerator and recipe package in the following order:
   1. Oracle EXT_SYS ATP Error Message Handler
   2. Oracle REST Ext_Sys Target_Integration_OICBEA2. The endpoint of this integration to be mentioned in the Config table (sample recipe integration for testing configured with an external system Id as OICBEA2).
   3. Oracle REST Ext_Sys Target_Integration_ERPARI. The endpoint of this integration to be mentioned in the Config table (sample recipe integration for testing configured with an external system Id as ERPARI).
   4. Oracle ATP REST Dispatcher
   5. Oracle REST ATP Producer
   6. Oracle ATP REST Orchestration
   7. Oracle EXT_SYS ATP Dispatcher Log Status
   8. Oracle Hospitality ATP Capture BE
9. Start the Connectivity Agent for the Hospitality Adapter Trigger to begin polling.
10. Activate the Listener integrations to capture the business events:
    1. Oracle Hospitality REST Listener_OICBEA2 (sample recipe integration for testing purposes - configured with an external system Id as OICBEA2)
    2. Oracle Hospitality REST Listener_ERPARI (sample recipe integration for testing purposes - configured with an external system Id as ERPARI)
    Once the Accelerator setup is complete, the Business Events will be dequeued from OPERA and will be processed by the Accelerator in the same order as they are dequeued from OPERA for processing.
    For testing, the external system currently being implemented in the above recipe is ATP. The re-sequenced business events order can be verified from the ATP table.

    Note:

    • Ensure the Integrations that were Activated are NOT deactivated at any point during the runtime flow.

    • After fixing the error, DO NOT run any accelerator integrations manually except 'Oracle REST REST Error Flag Reset' integration.

    • In case of error, ensure you first deactivate the Listener Recipe Integration. Next, check that the 'ERR_STATUS' flag is 'Y' for that External System in the configuration table and then proceed to activate the 'Oracle REST REST Error Flag Reset' integration. After fixing the error, manually call this integration with the external system Id as a parameter to reset the flags and start business events processing.