In this section: |
A server or global profile, edasprof.prf, is created during installation. You can customize this profile which is applied to all users. Optionally, you can create separate profiles to customize the server environment for a role, a group of users or an individual user. You can also create service profiles, which specify settings for the server environment. For information, see Profile Level. Profiles are executed in the following sequence: server, service, role, group, and user.
A profile can include almost any command that a client application can send to the server, however, profiles are used most frequently for application set up commands such as SETs, search path set up, and DBMS connection information, which may vary by adapter.
Two key aspects of profile customization are level and associated search order. The server processes all profiles found in the search order. If it finds duplicate settings or commands, the last setting or command processed will be active for the connection.
When you create a profile, take into account that the more processing performed by the profile, the more time it takes for an application to connect to the server. An exception is pooled deployment, where only one profile is processed when the server agent initially starts or is refreshed.
How to: |
The server supports various levels of profiles to provide flexibility for designing and running production applications. The order in which the following profiles are listed correlates with the search order in which they are processed by the server when multiple profiles exist.
The first level of profile, the global profile, is a startup file that is automatically created during installation and configuration of the server. It contains default environment settings required for the correct operation of the server.
The global profile remains in effect throughout a user session. You can modify the global profile default settings. You can also add any commands or code that all connected users require before application processing begins.
Characteristic |
Description |
---|---|
Name |
edasprof.prf |
Location |
UNIX: $EDACONF/etc directory Windows: $EDACONF\etc directory IBM i: IFS $EDACONF/etc directory OpenVMS:
EDACONF [.ETC] directory
|
Override |
Set the environment variable EDASPROF to point to an alternate location of edasprof.prf (you cannot rename edasprof.prf). |
Sequence in search order |
First |
Scope |
Applies to all connected users. |
A service profile specifies settings for the server environment, but the settings in this level of profile apply only to users associated with a specific service. When a user connects to the server, 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. You can specify a service profile in the Web Console by selecting Configuration/Monitor from the Workspace menu, and Profile Settings from the navigation pane.
You can create a service profile using the Workspace menu Configuration/Monitor option. Expand Configuration Files and Server Profiles folders in the navigation pane. Right-click Server Profiles and select Edit. You can also use any standard system editor. If you use an editor, create the service profile in the correct location.
Characteristic |
Description |
---|---|
Name |
name.fex |
Location |
Follows the normal search path for procedures (focexecs). |
Override |
None |
Sequence in search order |
Second |
Scope |
Applies to all users of the same service. |
A role profile specifies settings for the server environment, but the settings in this level of profile apply only to users assigned to a specific role. When a user connects to the server, the role profile settings are applied and remain in effect throughout the user session.
A group profile specifies settings for the server environment, but the settings in this level of profile apply only to users associated with a specific security group. When a user connects to the server, the group profile settings are applied and remain in effect throughout the user session.
A group profile may contain settings that are the same as those in a global profile.
Server Administrators need to register group profiles and users to give them privileges that are different from those they inherit from their default role. Group profiles are used to set DBMS connections, variables, and other settings that should be executed for group users when they connect.
If you use an editor, create the group profile in the correct location.
Characteristic |
Description |
---|---|
Name |
group_name.prf |
Location |
UNIX: base_directory_name/ibi/profiles Windows: base_directory_name\ibi\profiles IBM i: IFS base_directory_name/ibi/profiles directory OpenVMS: base_directory_name [.IBI.PROFILES] directory
|
Override |
Set the edaserve.cfg keyword edaprfu to point to an alternate location of group_name.prf. |
Sequence in search order |
Third |
Scope |
Applies to all users of the same security group. |
A user profile specifies settings for the server environment, but the settings in this level of profile apply only to a specific user ID. When a user connects to the server, the user profile settings are applied and remain in effect throughout the user session.
A user profile may contain settings that are the same as those in a global profile.
You can create a user profile at any time as by:
The Edit New User Profile page opens.
The Create new user profile page opens.
You can also use any standard system editor. If you use an editor, create the user profile in the correct location.
Characteristic |
Description |
---|---|
Name |
user_id.prf |
Location |
UNIX: base_directory_name/ibi/profiles Windows: base_directory_name\ibi\profiles IBM i: IFS base_directory_name/ibi/profiles directory OpenVMS: base_directory_name [.IBI.PROFILES] directory
|
Override |
Set the edaserve.cfg keyword edaprfu to point to an alternate location of user_id.prf. |
Sequence in search order |
Fourth |
Scope |
Applies to a specific user. |
iWay Software |