Set the security flag

You need to set the security flag for this sample application so that users are allowed to view the operational data. The value to use for the flag depends on whether security was enabled for the Operations and Administration Console (OAC) when it was installed in IBM® WebSphere® Liberty.

The scripts and files that you need to use to set the security flag for this sample application are extracted from the FXH_Scheduled_Expectation_Sample_PI.zip file. For more information about the names of the database files that are provided for this sample application, see Installation files.

The following sections describe how to set the security flag for this sample application for each database platform.

Db2 database on UNIX

After extraction, the files are located in the configuration subdirectory for the Db2® LUW files.

Run the set security flag script by using the following syntax.

ApplyFTM_OpDataNoRestrict.sh [dbname] [dbschema] [SecurityFlag] > log.txt

Valid options for the SecurityFlag parameter are security_on and security_off. The security_on value must be used when security is enabled in IBM WebSphere Liberty.

Db2 database on the Windows operating system

After extraction, the files are located in the configuration subdirectory for the Db2 LUW files.

Run the set security flag script by using the following syntax.

ApplyFTM_OpDataNoRestrict.cmd [dbname] [dbschema] [SecurityFlag] > log.txt

Valid options for the SecurityFlag parameter are security_on and security_off. The security_on value must be used when security is enabled in IBM WebSphere Liberty.