Page History
...
Configuring the instance registry only affects the specific instance. Every element in the instance registry can also be specified in the server registry file, in which case it affects all the instances on that server.How to
To change instance registry1. On
- On the relevant Precise node (proxy), manually change the products\i3fp\registry\instances\www\
...
- <server-
...
- name>\
...
- <instance_
...
- name>\settings.xml file.
...
- Save the file.
...
- Run the
update-main-registryCLI command on the same Precise node.- UNIX. /infra/bin/psin_cli.sh -action update-main-registry -i3-user admin -i3-clear-password admin -registry-path /registry/clusters/www/
...
- <server_
...
- name>/
...
- <instance_
...
- name>
- Windows. infra\bin\psin_cli.bat -action update-main-registry -i3-user admin -i3-clear-password admin -registry-path /registry/clusters/www/
...
- <server_
...
- name>/
...
- <instance_
...
- name>
This will force a registry sync from the node's FocalPoint to the main FocalPoint.
Cluster registry
Configuring the cluster registry affects all instances of the specific cluster.
| Info |
|---|
...
All instances in the cluster need to be restarted via AdminPoint after changing the cluster registry. |
How to To change the cluster registry:1. On
- On the relevant Precise node (proxy), manually change the products\i3fp\registry\clusters\www\
...
- <cluster-
...
- name>\settings.xml file.
...
- Save the file.
...
- Run the
update-main-registryCLI command on the same Precise node.- UNIX. ./infra/bin/psin_cli.sh -action update-main-registry -i3-user admin -i3-clear-password admin -registry-path /registry/clusters/www/
...
- <cluster_
...
- name>
- Windows. infra\bin\psin_cli.bat -action update-main-registry -i3-user admin -i3-clear-password admin -registry-path /registry/clusters/www/
...
- <cluster_
...
- name>
This will force a registry sync from the node's FocalPoint to the main FocalPoint.NOTE Cluster
| Info |
|---|
Cluster registry changes override the FocalPoint registry changes. |
connection-params (in general section)
The following table describes the registry elements for the connection-params (in the general section).
Table 9-1 connection1 connection-params (in general section)
| Registry |
|---|
...
| element | Description |
|---|---|
| site- |
...
| name | Specifies the name of the Web application (context root). Only relevant for J2EE Web servers and only when the filter is not installed on the root Web application. |
| filter-connect-ext-cmd- |
...
| line | Additional miscellaneous command line parameters for the psi_web_filter_connect utility which is used to send management URLs to the filter. |
| authorized- |
...
| ips | Comma separated IPs list that specifies the IPs from which the Precise for Web agent management pages can be browsed. Other IPs that will try to access this status will be blocked. (127.0.0.1 is added by default). |
ssl (in connection-params, in general section)
The ssl element in the registry is a "container" element that contains the use-client-certificate, cipher-list, and log-file elements. It also contains another "container" element: client-certificate. This "container" element contains the path, password, and key-path elements.
The following table describes the registry elements that can be used for the ssl instance registry.
Table 9-2 ssl 2 ssl elements
| Registry |
|---|
...
| element | Child element | Description |
|---|---|---|
| use-client- |
...
| certificate | Specifies the use of a client certificate when Precise for Web tries to connect using |
...
Secure Socket Layer (SSL). Default value: false. |
| cipher- |
...
| list | Specifies additional ciphers that OpenSSL uses on top of the default ciphers for SSL |
...
version 2 and 3 and Transport Layer Security (TSL) version 1. For more information, see the following URL: http://www.openssl.org/docs/apps/ciphers.html#cipher_suite_names. |
| log- |
...
| file | Specifies the file that OpenSSL logging is written to. | |
| client- |
...
| certificate | Specifies client certificate details, if the monitored Web server requires it. Container for path, password, and key-path elements. |
...
| path | Specifies the full path of the client certificate. |
...
| password | Specifies the password to be used to decrypt the certificate file. The password itself should be encrypted using the Encrypt command that is part of the Precise CLI Utility. For more information, see the Precise CLI Utility Reference Guide. | |
...
| key-path | Specifies the path to the private key if it is different than the path to the certificate. |
user-authentication (in connection-params, in general section)
The following table describes the registry elements for the user-authentication (in connection-params, in general section).
Table 9-3 user3 user-authentication (in connection-params, in general section)
| Registry |
|---|
...
| element | Description |
|---|---|
| user | Specifies the user name for authentication. |
...
| password | Specifies the user password for authentication. The password itself should be encrypted using the Encrypt command that is part of the Precise CLI Utility. For more information, see the Precise CLI Utility Reference Guide. |
| domain |
...
| Specifies the domain name for authentication. |
...
| method | The authentication method. |
...
One of the following methods should be used:
|
Server-side
The following table describes the registry elements for the server-side .
Table 9-4 Registry 4 Registry elements for server-side
| Registry |
|---|
...
| element | Description |
|---|---|
| ext- |
...
| list | Specifies the extensions used, such as .html, .jsp, and .asp. For example: <ext-list>html,jsp,asp</ext-list> Default values: html, swe, asp, aspx, htm, jsp, php, gbl, cfm, pl, php3, do, IScript_PT_NAV_PAGELET, I_Script_AppHP, IScript_UniHeader_Frame, IScript_PT_NAV_INFRAME, iscript_apphp, iscript_timeoutwarning |
| ext-list- |
...
| separator | Specifies the separator of the extension list. Default value: , (a comma) |
| stat- |
...
| extension | Specifies the URL of the statistics module. Add this registry element only if you know that the statistics URL differs from the default URL for the specific Web server type. Default values: Apache: server-status?auto iPlanet: .perf WebLogic: weblogicstat WebSphere: websphere_stats |
| filter- |
...
| trace | Specifies whether filter logging is used. Default value: false |
| filter-session- |
...
| cookie | Specifies the name of the session cookie used by the application. Define this value to improve client-side correlation in the following Web servers: WebLogic, WebSphere, Tomcat, Oracle AS, Sun One, IIS, Apache 2.x. Default value: JSESSIONID |
| max-i4w-cookie- |
...
| size | Specifies the maximum size of a Precise for Web cookie (in bytes). Default value: 2048 |
| filter-ignore- |
...
| files | A comma-separated list of files that the filter has to ignore. If a file contains any of these patterns, it is ignored. Only relevant for J2EE filters. |
| filter-use- |
...
| encoding | Specifies the translation of URLs and URL parameters to unicode format. Set this parameter if |
...
URLs or parameters may contain non-ASCII characters. Default value: false |
| filter-encoding- |
...
| name | Specifies the name of the URL encoding mechanism. Set this parameter if the server handles |
...
URLs that use neither UTF-8 nor local encoding, which are the default encoding types. |
| web-parameter- |
...
| delimiters | A list of URL parameters delimiters. These delimiters are used to separate the parameters of a |
...
URL from the URL itself. For example, the URL: “index.html?param1=abc” has 1 parameter |
...
‘param1’. The parameters delimiter in this URL is ‘?’. Use this element if your application uses |
...
non-standard delimiters (like ‘;’). To specify more than one delimiter, concatenate all delimiters into one string, for example: <parameter-delimiters>?;.</parameter-delimiters> sets 3 delimiters: ‘?’, ‘;’ |
...
& ‘.’ If more than 1 delimiter is used, the first one that is encountered in the URL is used. Default value: ? (question mark) |
| collect-post- |
...
| parameters | If this registry element is set to true, the filter collects parameters that are passed in the request body (as opposed to parameters that are passed with the URL). For enabling the post-parameters collection on an IIS Web server, another action is needed (besides changing this flag) - For more information, see the Adding post-parameters collection for IIS6 and Adding post-parameters collection for IIS7 sections in the Installing Web Tier Collectors section of the Precise Installation Guide. Default value: false (for Siebel this is set to “true” (automatically)) |
...
|
...
|
...
|
...
| ||
| apache-pid-file- |
...
| path | Sets the path for apache .pid file (commonly: httpd.pid). Should be set only when the .pid file path is not specified in the configuration file or in any other case, when the statistics agent fails to resolve it. |
user-defined-transaction-name
By configuring the elements user-defined-transaction-name, you can change the collection method of the transactions. This is valid for Precise for Web and Precise TPM. The collection method can be represented by one of the following tags:
Table 9-5 Elements
Elements Description
cookie-name Collects the value of the specified cookie.
req-header-name Collects the value of the specified request header.
parameter-name Collects the value of the specified GET parameter (not relevant for POST parameters).
dom-element Collects the value of the specified dom element. Applicable only if the client.-side agent is installed.
display-mode The way the transaction name is displayed in Precise for Web and Precise TPM.
...
<user-defined-transaction-name>
<dom-element>document.title</dom-element>
<display-mode>prefix</display-mode>
</user-defined-transaction-name>
If the client-side agent is not installed on your Web server (only server-side is installed), you can not collect the Title DOM element.
user-defined-client-ip
By configuring the element user-defined-client-ip, you can change the way that client IP is collected by the server-side agent. You can instruct Precise for Web to collect the client IP from 3 different sources (instead of the HTTP request itself):
...
NOTE You may want to change the way the client IP is collected when the Web server is behind some proxy, in which case the collected client IP is always the IP of the proxy.
apache-virtual-hosts
To separate Apache Virtual Hosts in different Precise applications, the Precise administrator needs to perform the following steps:
1. Create an Application in Precise for each Virtual Host. (For more information, see the Working with the Application Installer wizard section in the Precise Installation Guide.)
2. Place the Apache instance in the multiple instance view in each of the defined Precise applications.
3. Go to the instance registry and set the a registry entry for each of the Virtual Hosts using the following format:
<virtual-host-settings>
<vhost-i>
<vhost-name>name</vhost-name>
<precise-application-name>application_name</precise-application-name>
</vhost-i>
…
<!-- map all unmapped Virtual Hosts to this env (if not defined the information will be discarded) -->
<vhost-i>
<vhost-name>default</vhost-name>
<precise-application-name>application_name</precise-application-name>
</vhost-i>
<virtual-host-settings>
NOTE In a case of an unmapped Virtual Host, transactions can either be displayed in the “default” application (“default” is set), or discarded if “default” is not set.
4. Restart the Web Collector on the monitored server by performing the following steps:
c. Go to AdminPoint>Agents.
d. Click Stop to stop all Web agents on the monitored server.
e. Click Start to start all Web agents on the monitored server.
After performing these steps, you will see the unique information of each Virtual Host in each of the defined Precise applications.
...