The w3Apps file determines which subroutines in a master dictionary are actually FlashConnect applications. The attributes for this file are defined in the table below:
Attribute |
Name |
Description |
0 |
Application |
Each FlashConnect dynamic application must be included in this file. If not included, it is not run by the D3 server. |
1 |
Anonymous |
Setting this attribute to Y (yes), allows anyone with network access to run the application without being authenticated through FlashConnect first. |
2 |
Users |
D3 MultiValued list of users that can use this application. Each user listed must also appear in the w3users file. |
3 |
Groups |
D3 MultiValued list of groups that can use this application. Each group must also appear in the w3Groups file. |
4 |
Desc |
Description of this application. |
5 |
Acct |
Specifies the account in which to run the application. If not specified, the application runs in the www account. The account must be a real account in either the VME (D3 or mvBase) or the FSI (D3). |
6 |
AcctPass |
If an Acct is specified and there is a password to the account, the password must be entered here (in non-encrypted form). |
7 |
Profile |
Specifies whether or not to track user logon information about this application.
|
8 |
Options |
|
D |
Stops the w3Monitor from automatically terminating the connection if the application drops into the system or Pick BASIC debugger. Also enables logging of incoming CGI and form variables, and outgoing HTML to the w3Logs,Dump file and disables caching. |
|
L |
Same as the D option, except:
|
|
S |
Enables the logon screen using Secure Socket Layers (SSL) for both anonymous and secured applications. |
|
9 |
Program |
Used if the application to execute does not have the same name as the w3Apps Item-ID. The program name attribute follows one of these formats:
For example:
This attribute allows several versions of the same application, such as demonstration, production, and development, to reside on the same database server. |
10 |
Timeout |
If profiling (attribute 7) is enabled, the password stored in the w3Profile file for this application is valid only for the specified number of minutes after the application stops. If zero or blank, the password never times out. |
Passwords
If the account that a w3Apps entry references has a password, these rules apply:
The account and password must be specified in each w3Apps item, even if the account is the www master account.
If the w3Apps account field is empty, the FlashConnect www master account is assumed. However, if this is the case, the account cannot have a password.
Before logging to a new account, FlashConnect verifies that the new account is not the current account.
If the account is the current account, the account is not changed.
If the account is not the current account, the account is changed.
While this increases performance, no automatic processing is performed when logging to the new account if the same account is used again.
Before logging to a new account, the account password in the w3Apps file is compared to the account's actual password.
If the match is valid, the account is changed.
If the match is not valid, the account is not changed, the application is not run, and an error is logged.
WARNING |
Passwords are stored in plain text in the w3Apps file. To protect this information, there must be a valid dm user in attribute 5 of the file control block for the w3Apps file. See the D3 Reference Manual for additional information about retrieval-locks. |
See Also