In this section: |
The following profiles can be used to configure default behavior on the WebFOCUS Server:
WebFOCUS Server global profile (edasprof.prf). The global profile is a startup file that is automatically created during Server installation. It contains the default environmental settings for the Server. The global profile remains in effect throughout a user session.
WebFOCUS Server service profile. A service profile is a file used by the Server to specify environmental settings for connections associated with a specific service. When the Client connects to the Server with a service qualifier, the service profile settings are applied and remain in effect throughout the user session. A service profile may contain settings that are the same as those in a global profile.
WebFOCUS Server group profiles. A group profile is a file used by the Server to specify environmental settings for users in a specific security group. Upon connection to the server by a user, the group profile settings are applied. They remain in effect throughout the Server session. Group profiles may contain settings that are for the most part defined by the same set of commands as those used in a global profile. This profile is only available if security is ON. For more information about group profile processing, see the Server Administration manual for your operating system.
WebFOCUS Server individual user profiles (userid.prf). A user profile is a file used by the Server to specify environmental settings for a specific user ID. When the user connects to the Server, the user profile settings are applied. They remain in effect throughout the user session. User profiles may contain settings that are for the most part defined by the same set of commands used in a global profile.
For more information, see the Server Administration manual for your operating system.
How to: |
Secure requests sent from the Client to the Server can include a list of variables and their associated values that enable the Server profile, using conditional logic, to activate different DBMS settings and create a customized server environment. For example, one set of values could activate a test environment and a different set of values could activate a production environment.
For Managed Reporting Requests, these variables, their associated values, and DBMS connection information, can be defined in the Managed Reporting Workspace from which the request originated. For APP requests, they can be defined in the HTTP Host Header from which the request originated. The variables and their associated values must be established on a Client, and the values assigned to variables by that client must not be overridden when included in a URL. A Client can deliver a unique set of variables and their associated values to an individual server or to all servers.
To configure support for the use of variables in client requests, an Administrator must type a list of variables in the Custom Settings list to include in requests submitted by that client to the Server, identify the variables to send to all Servers, identify those to send to individual Servers, and identify the database containing those variables in the Server profile.
Only an administrator can configure a list of variables and their associated values for a client.
#variables and values
VariableName=Value
Where:
Is the name of a variable that you want to send from this client. This variable must appear in the database of variables connected to the Servers that will receive these requests.
Is the specific value for the variable that you want to send from this client.
For example:
#variables and values
IBI_pvar=XPROFILE
IBI_clientName=Client1
ABCVar=Test2
#List of profile variables to be sent to all eda servers
IBIC_profileVars=Variable1;Variable2;…
Where:
Is a variable defined in the list of variables and values.
For example:
#List of profile variables to be sent to all eda servers
IBIC_profileVars=IBI_pvar;IBI_clientName;
#list of profile variables to be sent ONLY to server named ServerName
Where:
Is the name of the specific server to which the list of variables must be sent.
IBIC_profileVars_ServerName=Variable1;Variable2;
Where:
Is the name of the specific server to which the list of variables must be sent.
Is a variable defined in the list of variables and values.
For example:
#list of profile variables to be sent ONLY to server named EDASERVE
IBIC_profileVars_EDASERVE=ABCVar;
The administrator must also update the server profile by adding the following statement to the end of the Server Profile list.
APP FILEDEF &IBI_pvar bugs/DatabaseName.dat
Where:
Is the name of the database linked to the Server.
For example:
APP FILEDEF &IBI_pvar bugs/edasprof.dat