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 WebSphere® Application Server.

The scripts and files that you need to use to set the security flag for this sample application are extracted from the FXH_Fragment_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 WebSphere Application Server.

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 WebSphere Application Server.

Db2 database on z/OS

After extraction, these files are located in the configuration subdirectory for the Db2 z/OS® files.

Use the following JCL files for z/OS.
  • @FTMSJCL
The member to use when the @FTMSJCL job is run depends on whether WebSphere Application Server security is enabled. The following list shows which member to use.
WebSphere Application Server security is not enabled
In this case, use the VALLNSEC member to configure all users to see all operational data.
WebSphere Application Server security is enabled
In this case, use the VALLSEC member to configure all users to see all operational data.
The @FTMCONF job must be run twice. Once for the CONFIG member and then again for the FRGCOMIT member.
Note: The order is important.

Oracle database on UNIX

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

Run the set security flag script by using the following syntax.
ApplyFTM_OpDataNoRestrict.sh [dbname] [dbschema] [dbuserID] [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 WebSphere Application Server.

Oracle database on the Windows operating system

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

Run the set security flag script by using the following syntax.
ApplyFTM_OpDataNoRestrict.cmd [dbname] [dbschema] [dbuserID] [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 WebSphere Application Server.