Split (1)

train · 94.6k rows

text stringlengths 65 20k
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error- free.No support is provided for this recipe.Overview This recipe demonstrates how to use Oracle Integration to create workers in Oracle HCM Cloud.The integration handles different types of workers including permanent employees, contingent workers, and pending workers.The integration performs the following actions: Reads a file from an external FTP server that contains data for new workers.Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.
The recipe is meant only for guidance, and is not warranted to be error- free.No support is provided for this recipe.Overview This recipe demonstrates how to use Oracle Integration to create workers in Oracle HCM Cloud.The integration handles different types of workers including permanent employees, contingent workers, and pending workers.The integration performs the following actions: Reads a file from an external FTP server that contains data for new workers.Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.
No support is provided for this recipe.Overview This recipe demonstrates how to use Oracle Integration to create workers in Oracle HCM Cloud.The integration handles different types of workers including permanent employees, contingent workers, and pending workers.The integration performs the following actions: Reads a file from an external FTP server that contains data for new workers.Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.
Overview This recipe demonstrates how to use Oracle Integration to create workers in Oracle HCM Cloud.The integration handles different types of workers including permanent employees, contingent workers, and pending workers.The integration performs the following actions: Reads a file from an external FTP server that contains data for new workers.Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.
The integration handles different types of workers including permanent employees, contingent workers, and pending workers.The integration performs the following actions: Reads a file from an external FTP server that contains data for new workers.Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.
The integration performs the following actions: Reads a file from an external FTP server that contains data for new workers.Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.
Transforms and formats the file to generate the REST payload.Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.
Create the appropriate individuals with worker types within Oracle HCM Cloud.System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.
System and Access Requirements Oracle Integration Oracle Fusion Cloud Human Capital Management, Release 13 or later FTP server Employee record payload files Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.
Related Documentation PDF documentation and supporting filesAppendix A Human Capital Management (HCM) Recipes A-186Transform an Oracle HCM Cloud Extract File to an ANSI 834 Benefits File Use this recipe to generate and format an ANSI 834 benefits provider input file, based on an Oracle HCM Cloud Extract file loaded from an FTP server.Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.
Note: This recipe is available as Oracle HCM Cloud FTP Server \| Export Benefits ANSI 834 in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.
No support is provided for this recipe.Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).
Overview HCM users require the ability to synchronize HCM benefits data with third-party benefits providers.These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.
These providers often expect data to be published using the ANSI 834 EDI Enrollment Implementation Format, which is the standard file format in the United States for electronically exchanging health plan enrollment data between employers and health insurance carriers.This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.
This recipe uses the data mapper capabilities of Oracle Integration to demonstrate how to transform a standard data extract from Oracle HCM Cloud into a Benefit Providers ANSI 834 data structure.The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.
The integration uses Oracle Integration with an FTP server to complete the following actions: Reads the HCM exported data.Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.
Transforms and formats the file in Oracle Integration mapper.Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.
Produces a valid ANSI 834 file.Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.
Uploads the file to the FTP server.For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.
For ease of setup, this recipe uses an FTP server to replicate the Oracle Fusion Cloud Human Capital Management instance.See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.
See the related documentation for details about how to use the Oracle HCM Cloud Adapter to retrieve files from an Oracle HCM Cloud instance via the HCM Extract tool.Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.
Also, this recipe uses no encryption.In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.
In a production environment, it is critical that you encrypt data at every stage.System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.
System and Access Requirements Oracle Integration FTP server Install, Configure, and Run the Recipe For more information and steps to install, configure, and run recipes, see Get Started with Integration Accelerators and Recipes .Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.
Related Documentation PDF documents and supporting filesAppendix A Human Capital Management (HCM) Recipes A-187Industries Recipes The Industries recipes help you quickly integrate various industry-specific applications.Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.
Topics: Generate Oracle Hospitality Access Tokens Generate Oracle Hospitality Access Tokens Use this recipe to generate an access token from the Oracle Hospitality Integration Platform (OHIP).Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.
Note: This recipe is available as Oracle Integration Oracle Hospitality \| Generate Access Tokens in the Integration Store.Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.
Oracle provides this recipe as a sample only.The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .
The recipe is meant only for guidance, and is not warranted to be error-free.No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.
No support is provided for this recipe.Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.
Overview You require an OHIP access token to call any Oracle Hospitality API.In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .
In addition, the tokens you obtain expire after sixty minutes.Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.
Using this recipe, you can automatically generate these tokens at a frequency of your choosing (for example, every thirty or sixty minutes), and use the tokens to seamlessly call the required Oracle Hospitality APIs.To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.
To use the recipe, you must install the recipe package and configure the connection and other resources within the package.Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.
Subsequently, you can activate and run the integration flow of the package manually or specify an execution schedule for it.When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.
When triggered, the integration flow queries OHIP for an access token (using the credentials configured in the recipe's resources) and returns the token details in a log message.After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.
After an integration instance successfully executes, you can view the log message containing the token through the Activity Stream.System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .
System Requirements Oracle Integration, Version 21.2.1.0.0 or higher Assumptions You have created an integration user account on the Oracle Hospitality Shared Security Domain (SSD) for the required hotel's tenant/chain, and possess a valid Integration ID and Integration Key for the account.See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .
See Partner Self-Registration Guide on the Oracle Hospitality Shared Security Domain (SSD) for OPERA documentation page.You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.
You have added a new environment in the Oracle Hospitality Developer Portal to access the hotels environment, and obtained the Gateway URL, Client ID, and Client Secret of the environment added.See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.
See Adding an Environment and Viewing Environment Details in Oracle Hospitality Integration Platform User Guide .Appendix A Industries Recipes A-188You have registered an application in the Oracle Hospitality Developer Portal (by selecting the right environment and subscribing to the required group of Oracle Hospitality APIs), and obtained the Application Key.See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.
See Registering an Application and Viewing the Application Key in Oracle Hospitality Integration Platform User Guide .Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.
Topics: Install and Configure the Recipe Activate and Run the Recipe Install and Configure the Recipe On your Oracle Integration instance, install the recipe package to deploy and configure the integration and associated resources.1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .
1.On the Oracle Integration home page, scroll to the Accelerators & Recipes section.2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.
2.Click Search All .3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .
3.Find the recipe package that you want to install.4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.
4.Select the package, and then click the Install icon.5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .
5.After the package is installed, click the Configure icon on the recipe card to configure the resources deployed by the package.The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .
The Configuration Editor page opens, displaying all the resources of the recipe package.Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.
Configure the following resources before you activate and run the recipe.Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.
Configure the Oracle REST Hospitality Connection Configure the Lookup Table Configure the Oracle REST Hospitality Connection 1.On the Configuration Editor page, select Oracle REST Hospitality Connection .2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.
2.Click Edit .The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.
The connection configuration page appears.3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.
3.In the Connection Properties section, enter the following details.Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.
Field Information to Enter Connection Type Leave REST API Base URL selected.Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .
Connection URL Enter the Gateway URL obtained from the Oracle Hospitality Developer Portal.See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.
See Assumptions .4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .
4.In the Security section, enter the following details.Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.
Field Information to Enter Security Policy Select Basic Authentication .Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.
Username Enter the Client ID obtained from the Oracle Hospitality Developer Portal.See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .
See Assumptions .Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.
Password Enter the Client Secret obtained from the Oracle Hospitality Developer Portal.Appendix A Industries Recipes A-1895.Click Save .If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.
If prompted, click Save for a second time.6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.
6.Click Test to ensure that your connection is successfully configured.A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.
A confirmation message is displayed if your test is successful.7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.
7.Click Back to return to the Configuration Editor page.Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.
Click Save again if prompted.Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.
Configure the Lookup Table Edit the lookup table to enter the necessary details.1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.
1.On the Configuration Editor page, select the lookup table and click Edit .2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.
2.Against the X-App-Key field, enter the Application Key obtained from the Oracle Hospitality Developer Portal.See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .
See Assumptions .3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.
3.Against the ToEmailID field, enter the email address to which run-time exception emails are to be sent.4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.
4.Against the FromEmailID field, enter the email address from which run-time exception emails are to be sent.5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.
5.Click Save .If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .
If prompted, click Save for a second time.6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.
6.Click Back to return to the Configuration Editor page.Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .
Activate and Run the Recipe After you've configured the connection and the lookup table, activate the recipe package and run it.1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.
1.On the Configuration Editor page, click Activate in the title bar.In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.
In the Activate Package dialog, click Activate again.A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.
A confirmation message is displayed informing that the integration has been submitted for activation.Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.
Refresh the page to view the updated status of the integration.2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .
2.Update the integration property values.a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.
a.On the Configuration Editor page, select the integration flow.b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.
b.Click Actions , then click Update Property Values .c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.
c.In the Update Property Values dialog, enter the appropriate values for the following integration properties.Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.
Click on a property row to expand it, and enter the appropriate value in the New Value field.Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.
Repeat for all property rows.GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.
GrantType: Enter "password" .Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.
Username: Enter the Integration ID of the integration account created on Oracle Hospitality Shared Security Domain.See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .
See Assumptions .Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.
Password: Enter the Integration Key of the integration account created on Oracle Hospitality Shared Security Domain.d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.
d.Click Submit .Appendix A Industries Recipes A-190A confirmation message is displayed informing that the integration properties have been updated successfully.3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .
3.Run the recipe.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .The Activity Stream pane appears displaying the access token as a log message.
a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .The Activity Stream pane appears displaying the access token as a log message.You can use this access token to call the required Oracle Hospitality APIs.
b.Click Run , then click Submit Now .c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .The Activity Stream pane appears displaying the access token as a log message.You can use this access token to call the required Oracle Hospitality APIs.See Calling Oracle Hospitality APIs .
c.In the resulting dialog, click Submit Now again.Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .The Activity Stream pane appears displaying the access token as a log message.You can use this access token to call the required Oracle Hospitality APIs.See Calling Oracle Hospitality APIs .Related Documentation Using the REST Adapter with Oracle Integration Oracle Integration Starter Recipes The starter recipes are basic integrations that required no additional setup.
Note that the Ad hoc request radio button is selected by default.You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .The Activity Stream pane appears displaying the access token as a log message.You can use this access token to call the required Oracle Hospitality APIs.See Calling Oracle Hospitality APIs .Related Documentation Using the REST Adapter with Oracle Integration Oracle Integration Starter Recipes The starter recipes are basic integrations that required no additional setup.Use them to see how easy it is to activate, run, view results, and monitor an integration between endpoints.
You've now successfully submitted the integration for execution.You can also schedule this integration to run at a date, time, and frequency of your choosing.See Define the Integration Schedule.4.Monitor the execution of the integration flow and view the access token.a.On the Configuration Editor page, select the integration flow.b.Click Run , then click Track Instances .c.On the Track Instances page: i.You'll see the integration flow of the recipe being triggered and executing successfully.The recipe now fetches an access token from OHIP.ii.Select the row of the integration instance that just executed, and click View Details .The Activity Stream pane appears displaying the access token as a log message.You can use this access token to call the required Oracle Hospitality APIs.See Calling Oracle Hospitality APIs .Related Documentation Using the REST Adapter with Oracle Integration Oracle Integration Starter Recipes The starter recipes are basic integrations that required no additional setup.Use them to see how easy it is to activate, run, view results, and monitor an integration between endpoints.Topics: Calculate Total Balance Concatenate Messages Echo Request Get Incident Details Get Weather Data Increment the Sequence Variable within a Loop Integration Perform Mathematical Operations Get Stocks Data Say Hello World Say Hello World InvokeAppendix A Oracle Integration Starter Recipes A-191Say Hello World Map Data Invoke Send Files from Your Application by Email Transfer a File Use Multiple Verbs and Resources Invoke Work with Files on FTP Servers Calculate Total Balance Use this recipe to calculate the total balance for a group of credit cards using the for each action, and log the result to the activity stream.

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.