...
The environment variable PROFOUNDJS_COMM_HOST specifies the Profound.js host name or IP address to connect to. The environment variable PROFOUNDJS_COMM_PORT specifies the port number to connect to.
Both environment variables are automatically set at the system level when you first install Profound.js. If you only installed one copy of Profound.js, there is no need to work with environment variables as they should already point to the correct Profound.js instance.
Each interactive Genie session inherits the system environment variable values, which then become the initial job environment variable values. You can view your current environment variable settings by using the interactive command WRKENVVAR.
...
You can select option 2 (Change) or use the CHGENVVAR command on PROFOUNDJS_COMM_HOST and PROFOUNDJS_COMM_PORT to change which Profound.js instance to connect to. CHGENVVAR can be used from a command line or in a CL program. This enables you to switch between instances, such as Production, Development, and Test.
The environment variables are changed at the *JOB level by default. In that regard, it is similar to changing a job's library list, meaning that the change affects the current user's session only.
HTTP/CGI Environment Variables
By default, if PJSCALL and proxy programs are called within a Genie application/interactive job and the Profound UI / Genie library is on the library list, any environment variables defined in the Genie HTTP/CGI job will be brought over to the calling job. To disable this behavior, you can set the environment variable PROFOUNDJS_SET_HTTP_VARS=0 in the calling job.
HTTPS in Genie
| Info |
|---|
ThePROFOUNDJS_COMM_VERIFYPEER and PROFOUNDJS_COMM_VERIFYHOST environment variables were added in Profound.js 5.8.2 |
In order to specify that Genie should connect via HTTPS, you will need to use the PROFOUNDJS_COMM_SECURE environment variable. To use HTTPS, set PROFOUNDJS_COMM_SECURE to 1.
The default SSL CA (certificate authority) certificates that Profound.js trusts are bundled with the product. The bundle includes the well known CAs and so should work fine if your server SSL certificate is issued by a well known authority. If your server is using a certificate issued by an unknown authority (such as a local/self-managed authority) you can override the CA certificates by setting the PROFOUNDJS_COMM_KEYRING environment variable. This variable can be set either to a file path on the IFS or to the special value *SYSTEM to use the CAs from the Digital Certificate Manager's *SYSTEM store. The keyring file must be in the IBM key database (KDB) format. For example:
...
...
Use *SYSTEM Store for CAs
| Code Block | |
|---|---|
ADDENVVAR ENVVAR(PROFOUNDJS_COMM_KEYRING) VALUE(*SYSTEM) | |
| title |
Use Alternate KDB File for CAs
| Code Block |
|---|
ADDENVVAR ENVVAR(PROFOUNDJS_COMM_KEYRING) VALUE('/MyDir/MyCAs.kdb') |
...
By default, the Profound.js Connector will verify that the server's SSL certificate is issued by a trusted authority and that the host name used on the request matches the host name the server's certificate was issued for. This ensures secure communications. However, in some cases (i.e. when using a self-signed server certificate) it may be necessary to disable these verifications. The following environment variables can be used:
PROFOUNDJS_COMM_VERIFYPEER: Set to '0' to disable SSL certificate verification.
PROFOUNDJS_COMM_VERIFYHOST: Set to '0' to disable SSL host name verification.
Note: Disabling SSL certificate and host name verification makes communications insecure and is strongly discouraged! Do not disable these verifications unless you understand/accept the risks.
Connecting to a development instance on your PC
...