Hi,
IntegrationServer requires only a very few data to be present in the database prior to first startup as it is storing most if its configuration/data under the following directories:
- IntegrationServer/config
- IntegrationServer/audiit/data
- IntegrationServer/DocumentStore
- IntegrationServer/WmRepository4
- IntegrationServer/XAStore
Only the Package WmTNWeb requires a specific entry to be set manually in the table IS_DATASTORE as it will not create/update its own configuration otherwise.
But this packages is deprecated and does no longer exist in versions wM 9.x and newer.
Not all of the directories mentioned contain static data, some are only buffering directories between IS and Database/Broker/UM.
Not all of them apply to all current wM versions.
The IS might throw an exception during startup when the MWS-Schema (used for CentralUsers function) has not been initialized yet or is not accessible at all maiking it impossible to monitor proeses et al. in MWS.
The MWS is working the other way round, because it is storing most of its configuration in the database except for those files which are placed in the file system explicitly.
Therefore when planning to point the mws to a new schema it is either possible to get the schema exported from the old db to the new db (assuming they are of same type and version) or re-configure the MWS againts the empty schema after a reinstallation.
After uninstalling MWS it is recommended to recreate the schema prior to do the fresh installation as it can be that the installation script tries to create some data in the database during installation (this is definitely true when installing Optimize, as earlier versions of the Optimize UI created the neccesary tables during the installation instead of having them included in the DCC/DBS-scripts for “PRODUCT MWS”).
Regards,
Holger
#webMethods#Integration-Server-and-ESB#webMethods-Architecture#webMethods-General