![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The staffpms file, which is located in the SWDIR\etc directory, specifies a number of different configuration options.
To modify the staffpms file:Y0NN5YNY??0AY
• Y, iProcess users must supply their password when they log in to this TIBCO iProcess Engine node.
• N, passwords are not required on login.
This character must be set to Y. Multiple logins must be enabled for iProcess Engine to operate.
The Use working days flag is set in the Procedure Manager, on the Status tab of the Properties dialog. For more information see “Use Working Days Flag” in TIBCO iProcess Modeler Procedure Management.Line 5 ends with a 7-character string that defines the working week. There is one character for each day of the week, running from Sunday (on the left) to Saturday (on the right). Y indicates that the day is a working day, N indicates that it is a non-working day. The default entry specifies a working week of Monday to Friday, as shown below.Line 5 of the staffpms file determines how the date is displayed in iProcess Engine. (The following example is for a iProcess Engine for Windows).
To change the format, for example, to yyyy/mm/dd:
2. %2d-%2d-%4d\-\%s%s %s, %s\dmy\wdmy\%2d:%2d\:\ AM\ PM\Week\NYYYYYN
This field must always be 3 for a database version. Note: This login/account must be the same login/account as the iProcess Engine database schema owner (specified in position 4). The Oracle TNS identifier that iProcess Engine uses to connect to the Oracle instance holding the iProcess Engine database tables. This is the appropriate SERVICE_NAME entry in the tnsnames.ora file, which is located in the ORACLE_HOME\network\admin directory).Note: This entry is only used if iProcess Engine uses an Oracle database. Note: This entry is not used if iProcess Engine uses an Oracle database.
If you need to change the passwords that the iProcess Engine database schema owner or iProcess Engine database user use to connect to the database, follow this procedure:
4. Enter the new password for a iProcess Engine database schema owner (the login/account defined in position 4 of line 9 of the staffpms file).
5. Enter the new password for a iProcess Engine database user (the login/account defined in position 3 of line 9 of the staffpms file).The swconfig utility terminates and displays the following message.
The iProcess security umask value, which controls “world” access to iProcess files in and under SWDIR. “World” permissions on each file installed by or created by the iProcess Suite are set to the iProcess group name permissions for the file, modified by this umask value. For example, if this value is:
• 7 for high security. “World” has no access to iProcess files in and under SWDIR. This is the default.
• 0 for low security. “World” has the same access to each file in and under SWDIR as the staffwar group.
3. Change the appropriate value on line 12 of the staffpms file.
4. Run fixperms,which is located in the SWDIR\bin directory, to reset the ownership and permissions information on all files in and under SWDIR.The implications of these security values in staffpms are:
•
• All iProcess processes run with the UID of an iProcess Engine background user, even if the process is started by root. The only exceptions are the runcmd utility, which is located in the SWDIR\util directory, and the RPC_UDP_LI process, which run as root.
• All iProcess files and directories (that is, all files in and under SWDIR) are owned by either root or the iProcess Engine background user. Their group ID is set to the iProcess group (staffwar).
• All iProcess users who need access to iProcess files and directories must be members of the iProcess group (staffwar). For example, users who need to run swutil, or to use the SERVERRUN commands that access files under SWDIR.Lines 15 and 16 of the staffpms file define whether and how iProcess uses the integral User Validation API provided with the LDAPCONF utility.
• Variables such as SWDIR are not supported in this parameter.The following example (for a iProcess Engine for Windows) specifies that user validation will be performed against the swuvamod.dll file in the D:/iProcess/staff200/lib directory.The following example specifies that user validation will be performed against the UVAPI.dll file in the C:/Tibco/iprocess_nod1/util directory, and that the proxy users are supplied by swadmin.
• Develop an external validation package, see TIBCO iProcess User Validation API User's Guide.
• Install an external validation package, see installation guide for TIBCO iProcess User Validation API.
• Use the integral user validation API provided with LDAPCONF, see LDAPCONF Utility User’s Guide.
4. Open the staffpms file located in the SWDIR\etc directory. Then copy the absolute directory of the folder you created in step 3 to line 19 of the file.If line 19 is blank, then iProcess Engine will use the SWDIR\logs directory as the default log files directory.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |