Building TIBCO Foresight REST API Engine for Docker

This step builds the Foresight Instream/Foresight Translator engine that the Foresight REST API Docker image uses. Building the Foresight REST API engine requires that the customer's licensed versions of Foresight Instream (Standard or Healthcare) and/or Foresight Translator be installed on the machine where the Foresight REST API Docker image is to be built.

The Foresight REST API engine must be built (or rebuilt) when:

Foresight REST API is first installed on a machine.
An update or hotfix to Foresight Instream and/or Foresight Translator is released and installed on the machine where the Foresight REST API Docker image is being built.
For healthcare customers, whenever an update to the code tables or guidelines is released and installed on the machine where the Foresight REST API Docker image is being built.

Perform the following steps to build the Foresight REST API Engine:

Procedure

Download the TIB_fsrest_1.2.0.tar.gz file from the TIBCO eDelivery site, and extract the file contents to a folder.

To download the installation package, you require a username and password. In case you do not have it, contact TIBCO Technical Support.
For new Foresight REST API installations, or if the Foresight Instream and/or Foresight Translator installations have been removed, first install Foresight Instream (either Standard or Healthcare version) and/or Foresight Translator on the machine where the Foresight REST API docker image is to be built.

Update Foresight Instream and/ or Foresight Translator with any updates or hotfixes, or for healthcare customers, apply any code table or guideline updates.
Navigate to the <folder>/fsrest-1.2.0/images/scripts folder.

Note: You need to input the host mount path, then the content under images/services/fsrest/misc/FSRestDirs gets copied to the mount path before the Foresight REST API image is running, if there is no mount path, then you can input n or N. The following is the text displayed while installation:
Do you want to mount the FSREST resource directory outside of the container? Please input the path or (n)o.
Run the following command:
```
./build-fsrest-engine.sh
```

Follow the prompts, entering the locations where Foresight Instream and Foresight Translator are installed. If one of these packages was not installed on the system, enter 'none' for its location.

On entry of the Foresight Instream/Foresight Translator locations, the script displays a screen to approve the engine build:

** Specify the Instream and Translator installations to use in FSRest Engine

   Enter path of Instream installation to use or 'none': /home/username/FSRest/TIBCO/Instream920/instream/9.2
   Use Instream installation in '/home/username/FSRest/TIBCO/Instream920/instream/9.2' (y/n)? y

   Enter path of Translator installation to use or 'none': /home/username/FSRest/TIBCO/Translator4.1/translator/4.1
   Use Translator installation in '/home/username/FSRest/TIBCO/Translator4.1/translator/4.1' (y/n)? y

** Confirming components to be used to build FSRest Instream/Translator Engine:
     Instream source directory   = '/home/username/FSRest/TIBCO/Instream920/instream/9.2'  (Healthcare Version)
     Translator source directory = '/home/username/FSRest/TIBCO/Translator4.1/translator/4.1'

     Proceed to build FSRest engine (y/n/q)?

Did you find this helpful?

Yes No