These scripts automate the extraction and monitoring of Oracle HCM data.
Clone the whole repo to wherever you want or, at the very least, copy the /bin and /cfg folders.
Note that the scripts have configuration variables defined, named CONNECT_TIMEOUT and MAX_TIME. These drive the web service calls. The former defines how many seconds the script will wait on making each web service call, before reporting a connection timeout. The latter defines how the maximum time (in seconds) the script will wait for each individual web service call to complete. These may need to be adjusted, depending on the performance of Oracle HCM.
Runs the HCM extraction utility
- One curl call is made to trigger a data extraction
- A second curl call is repeatedly made to monitor the status of the extraction
The success of the script can be used as a trigger of a subsequent file transfer.
- -j HCM job name
- -l number of times to poll when checking status
- -p password
- -s host server endpoint url (inc https)
- -u username
- -w wait time (in seconds) between status checks
- 00 - if the extraction completes successfully
- 05 - if the extraction does not complete before the script ends
- 09 - if the call to HCM's APIs fails
- 99 - if something else has gone wrong
Runs HCM's BI reporting utility.
Script operates identically to hcm-extract.sh with the following changes:
- -f path and file name of SFTP location
- -n notification email address
- -r path and file name of the BI report file
- -t report template
Dockerfiles are included, to allow development and testing of the scripts on Windows.
These are based on a CentOS image, as it is assumed that the target environment is RedHat-based.
docker build -t hcm-extract -f ./Dockerfile-hcm .
docker build -t hcm-bi-extract -f ./Dockerfile-bi .
docker run -it --rm --name hcm-extract_1 hcm-extract [PARAMETERS]
docker run -it --rm --name hcm-bi-extract_1 hcm-bi-extract [PARAMETERS]