The asg-validate tool checks for a complete and correct configuration set using the Config UI before the configuration can be used by the Core Engine at run time.
The asg-validate tool loads the data from all the configuration (cfg) files for a gateway configuration project into the memory and validates it against each other. The
asg-validate also loads and compiles all the XSLT files for a gateway configuration project and therefore it checks if the XSLT files are valid.
The asg-validate tool ensures that the data in one configuration file that is dependent on the other configuration file is valid.
For example, you have defined a partner P_1 and assigned it to a partner group
PG_1 for a
myconfig project configuration. When you run
asg-validate for
myconfig project, it loads partner
P_1 data into memory and finds that this is assigned to
PG_1 partner group. Then it checks if the data of partner group
PG_1 is also available in the memory of the Core Engine. If it does not find
PG_1 partner group data, it throws an error indicating that partner group
PG_1 is not defined in Partner Groups.
You can use the asg-tools utility
to perform the validation for a gateway project configuration.
where asg_config_name is the name of the configuration to be validated.
For example, to validate the BookQueryBE configuration type the following command:
The output of the asg-validate tool is stored in a log file named
asg-validate.log. By default, this log file is located in the
ASG_CONFIG_HOME/
logs directory. You can change the location of the logs directory in the
ASG_HOME/
bin/asg_validation.cdd file by editing the dir parameter as follows:
The asg-validate mainly validates the integrity of data stored in the configuration files for a configuration set. This tool does not detect certain configuration issues such as invalid URL for a transport, invalid queue, or topic name for JMS services.
