Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This section describes the registry settings configuration process.

Registry structure and inheritance

Some configurations are relevant per instance (e.g. collect-post-parameters) and some are relevant for the J2EE collector in general (e.g. preferred-data-port). Others are relevant for the whole product (e.g. user-agents). Instance configuration resides in the instance registry file:

products\i3fp\registry\instances\j2ee\<server-name>\<instance_name>\<settings>.xmlNOTE    You

Info

You can set instance configuration in

...

the products\i3fp\registry\instances\j2ee\<server-name>\<settings>.xml file if you want to set the same setting for all instances on the machine. Consider however, that settings in the instance registry will override the settings in the server registry.

J2EE collector configuration resides in the registry file:

products\i3fp\registry\instances\j2ee\<server-name>\<settings>.xml

Info

...

You can set the configuration for all J2EE collectors at once by modifying the file

...

products\i3fp\registry\products\j2ee\focal-point.xml

Consider however, that settings in the server registry will override the settings in

...

the focal-point.xml file.

Product level configuration resides in the registry file: products\i3fp\registry\products\j2ee\focal-point.xml

J2EE collector behavior is set via the registry entry <j2ee-collector>

Cluster configuration resides in the registry file:

products\i3fp\registry\clusters\j2ee\<cluster-name>\<settings>.xml

Instance registry

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 change the instance registry
1.    On the relevant Precise node (proxy), manually change the products\i3fp\registry\instances\j2ee\<server-name>\<instance_name>\<settings>.xml file.
2.    Save the file.
3.    Run the update-main-registry CLI 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/j2ee/<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/j2ee/<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.
NOTE    All instances in the cluster need to be restarted via AdminPoint after changing the cluster registry.
To change the cluster registry:
1.    On the relevant Precise node (proxy), manually change the products\i3fp\registry\clusters\j2ee\<cluster-name>\<settings>.xml file.
2.    Save the file.
3.    Run the update-main-registry CLI 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/j2ee/<cluster-name>
•    Windows. infra\bin\psin_cli.bat -action update-main-registry -i3-user admin -i3-clear-password admin -registry-path /registry/clusters/j2ee/<cluster_name>
This will force a registry sync from the node's FocalPoint to the main FocalPoint.
NOTE    Cluster registry changes override the FocalPoint registry changes.

...