3 Install and Configure the Recipe
-
On your Oracle Integration instance, install the recipe package to deploy and configure the integrations and associated resources.
-
On the Oracle Integration Home page, in the Pick a Recipe/Accelerator section, click View All.
-
Find the recipe package that you want to install.
-
Hover over the recipe, then click Install
.
A message confirms that the recipe was successfully installed, and the recipe card shows INSTALLED.
-
Hover over the recipe again and click Configure
to configure the resources of the recipe.
The Configuration Editor page opens, displaying all the resources of the recipe package.
-
Configure the resources before you activate and run the recipe.
Configure the Oracle REST OIC API Connection
-
In the Configuration Editor, under Connections, hover over the connection, and then click Edit
.
-
In the Properties section, enter the following details:
Field Information to Enter Connection Type
Leave REST API Base URL selected.
Connection URL
Enter the host name of the Oracle Integration instance in which you’ve installed the recipe.
-
In the Security section, enter the following details:
Field Information to Enter Security Policy
Select Basic Authentication.
Username
Enter the username of the Oracle Integration user account with the Service Invoker role. See System and Access Requirements.
Password
Enter the password of the Oracle Integration user account with the Service Invoker role.
-
Click Save. If prompted, click Save again.
-
Click Test to test that the connection. A confirmation message appears if your test is successful.
-
To return to the Configuration Editor, click Go back
.
Configure the Oracle REST OIC Internal API Connection
-
In the Configuration Editor, under Connections, hover over the connection, then click Edit
-
In the Properties section, enter the following details:
Field Information to Enter Connection Type
Leave REST API Base URL selected.
Connection URL
Enter the host name of Oracle Integration instance in which you’ve installed the recipe.
-
In the Security section, enter the following details:
Field Information to Enter Security Policy
Select Basic Authentication.
Username
Enter the username of the Oracle Integration user account with the Developer role. See System and Access Requirements.
Password
Enter the password of the Oracle Integration user account with the Developer role.
-
Click Save. If prompted, click Save again.
-
Click Test to test the connection. A confirmation message appears if your test is successful.
-
To return to the Configuration Editor, click Go back
.
Note:
To use OAuth as the Security Policy, you can use it and configure it accordingly.Configure the Oracle HCM Cloud Connection MICROS
-
In the Configuration Editor, under Connections, hover over the connection, then click Edit
.
-
In the Connection Properties section, enter the Oracle Fusion Cloud HCM host name. For example:
https://your_domain_name.fa.DC.oraclecloud.com
-
In the Security section, enter the following details.
Field Information to Enter Security Policy
Select Username Password Token.
Username
Enter the username of the account created for Oracle Integration on Oracle Cloud HCM. See Configure Oracle Cloud HCM
Password
Enter the password of the account created for Oracle Integration on Oracle Cloud HCM.
-
Click Save. If prompted, click Save again.
-
Click Test to test the connection. A confirmation message appears if your test is successful.
-
To return to the Configuration Editor, click Go back
.
Configure the Oracle MICROS SOAP LABOR Connection
-
In the Configuration Editor, under Connections, hover over the connection, and then click Edit
.
-
In the Properties section, enter the following details:
Field Information to Enter WSDL URL
Provide the WSDL Endpoint you have captured earlier. See Configure MICROS Labor Management
-
In the Security section, enter the following details:
Field Information to Enter Security
Select Username Password Token
Username
Enter the Username Token you have captured earlier. See Configure MICROS Labor Management
Password
Enter the password you have captured earlier. See Configure MICROS Labor Management
-
Click Save. If prompted, click Save again.
-
Click Test to test the connection. A confirmation message appears if your test is successful.
-
To return to the Configuration Editor, click Go back
.
Configure the Lookup Tables
In the Configuration Editor, click Lookups to view the lookup tables in the recipe. Hover over the lookup table
to edit, then click Edit .
This recipe package contains the following lookup tables.
Oracle-BRT-HCM_MICROS_StoreMapping
This lookup holds the mapping between HCM Location Code and LM Location reference. The following table provides the description for each parameter:
Name | Description |
---|---|
HCMLocationCode |
Specifies the HCM Location Code. Example value: QSR Austin |
MICROSStore |
Specifies the MICROS Location reference for the corresponding HCM Location Code. Example value: SES_198 |
Oracle-BRT-HCM_Micros_Notification_Config
This lookup table contains the information needed to trigger the error handlers. The following table provides the description for each parameter:
Name | Description |
---|---|
OIC |
The email address for the OIC administrator that must be notified on failures. |
HCM |
The email address of the HCM administrator that must be notified on failures. |
MICROS |
The email address of LM administrator that must be notified on failures. |
Oracle-BRT-HCM_MICROS_JobMapping
This lookup table stores the mapping between HCM and LM job code, role mappings. The following table provides the description for each parameter:
Name | Description |
---|---|
HCMEmployeeType |
This parameter provides the different HCM Employee Type. Example value: Cashier |
EmployeeRole |
The role assigned to the employee in LM. Example value: Cashier |
EmployeeClass |
The POS employee class POSRef assigned to this employee’s POS configuration in LM. Example value: 301 |
EmployeePrivilege |
The POS privileges assigned to the employee in LM Example value: 20004 |
EmployeeRolePOSReference |
The POS reference for the employee role in LM Example value: 199 |
EnterprisePOSReference |
The enterprise POS reference for the job code assigned to the employee record in LM. Example value: 101 |
Oracle-BRT-HCM_AtomFeed_TimeStamp
This lookup holds the last successful processed entry from HCM Atom Feed. When integration is run it will query for all available entries starting from this timestamp in HCM.
Name | Description |
---|---|
System |
Specifies the last published entry in HCM New Hire Atom Feed that was processed successfully Example value: HCM Do not modify this value. |
TimeStamp |
Specifies the last successfully processed Atom Feed records published Time Stamp. Example value: 2022-05-13T11:19:14.829Z Update this value based on the date from which you would like to sync the Employee Records for your initial run. After initial run, the integration will pull the delta records from the last successful processed date. |