Copyright © Cloud Software Group, Inc. All Rights Reserved

Publish Project Configuration

The Publish project configuration enables you to send the configuration changes of a project to memory so that they are available to the Core Engine at run time without restarting the Core Engine.

You can publish and update the following changes at run time:

•	Publish Configuration

Using the Publish Configuration option, you can publish any configuration changes saved in the configuration files to an active Core Engine instance. After you make any changes to the configuration of a project, you do not need to start the Core Engine instance, as the Core Engine instance picks all the changes as soon as you publish the configuration.

•	Update Log Level

Using the Update Log Level option, you can dynamically change the levels of logging of the Core Engine at run time. For example, you can update the logging level from INFO to DEBUG at runtime for the Core Engine.

•	Update Central Log Level

Using the Update Central Log Level option, you can dynamically change the levels of logging of the Central Logger component at run time.

Publish Configuration

You can publish the configuration changes using the Config UI as follows:

1.	Start the Config UI. See Starting GUI.

2.	Move the mouse pointer on the gateway configuration project and select Publish Project Configuration icon.

3.	In the dialog box wizard, set the values for the fields as follows:

−	Type: from the drop-down list, select Publish Configuration.

−	Gateway URL: Enter the URL of the Core Engine instance where the configuration changes are to be published. For example, http://ASGServer:PortName

where ASGServer is the server machine and PortName is the port number for a running Core Engine instance.

4.	Click Submit.

• The Core Engine instance must be running with the same project configuration for which you published the configuration. • The configuration changes are published only to a single engine instance locally. To update the configuration changes to multiple engine instances running remotely in a cluster environment, see Update Project Configuration. • If you change the username and password to login to the Config UI, make sure to add the username and password in the ASG_HOME/mm/config/users.pwd file. See User Credentials File for File-Based Authentication.

Changing Log Level Settings

Using the Config UI, you can change the log level settings for the Core Engine and the Central Logger component. See the following topics:

•	Changing Log Level Settings for Core Engine.

•	Changing Log Level Settings for Central Logger.

Changing Log Level Settings for Core Engine

To change the log level settings for the Core Engine, follow these steps:

1.	Start the Config UI. See Starting GUI.

2.	Move the mouse pointer on your gateway configuration project and select Publish Project Configuration icon.

3.	On the dialog box wizard, set the values for the fields as follows:

−	Type: from the drop-down list, select Update Log Level.

−	Gateway URL: Enter the URL of the Core Engine instance where the log level settings are to be applied. For example,

http://ASGServerMachine:PortName

where ASGServerMachine is the server machine and PortName is the port number for a running the Core Engine instance.

−	Log Level: from the drop-down list, select the level of logging. For example, DEBUG.

See Logging Levels of Core Engine for types of supported logging levels.

4.	Click the Submit button.

Changing Log Level Settings for Central Logger

To change the log level settings, follow these steps:

1.	Start the Config UI. See Starting GUI.

2.	Move the mouse pointer on the gateway configuration project and select Publish Project Configuration icon.

3.	On the dialog box wizard, set the values for the fields as follows:

−	Type: from the drop-down list, select Update Central Logger Log Level.

−	Gateway URL: Enter the URL of the Core Engine instance where the log level settings are to be applied. For example,

http://ASGServerMachine:PortName

where ASGServerMachine is the server machine and PortName is the port number for a running Core Engine instance.

−	Log Level: Enter the level of logging from the drop-down list. For example, Detail Logging ON. See Central Logger Log Level.

4.	Click the Submit button.

• The Update log level settings for the Core Engine and the Central Logger are applicable only at run time. • When the Core Engine is restarted, the original log level settings for the Core Engine and the Central Logger component are picked up from the ASG_CONFIG_HOME/asg.properties and ASG_CONFIG_HOME/asg_cl.properties files respectively. − For the Core Engine, the log level setting is defined by the tibco.clientVar.ASG/Logging/MinLogLevel property in the ASG_CONFIG_HOME/asg.properties file. − For the Central Logger component, the log level setting is defined by the tibco.clientVar.ASG/Logging/clLogLevel property in the ASG_CONFIG_HOME/asg_cl.properties file.

Copyright © Cloud Software Group, Inc. All Rights Reserved