Resolved this error - This may be related to JDBC Pools Database Passwords being changed, or a copy of bad files referencing wrong connection information in the [saghome]/analysis/conf/components or [saghome]/analysis/conf/JDBC/pools directories.
These errors may also be related or fixed in this manner:
-
com.webMethods.sc.security.passman.PasswordManagerException: Wrapped Exception
-
(OPTIMIZE) [Analytic Engine v8.0.3.0.DimensionDefinitionCacheLoader.[SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00904: “DISPLAY_NAME”: invalid identifier
-
org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘definitionCache’ defined in file [saghome/optimize/analysis/conf/spring/core.spring.xml]: Invocation of init method failed;
-
(OPTIMIZE) [Analytic Engine v8.0.3.0.ConfigMigrator.configFileLoadPropertyError] 2013-01-13 11:38:29.968 EST WARN: Could not set property DDLStatementsOutputDirectory in configuration file DatabaseProperties
-
com.webMethods.bpo.database.SCGConnectionManager.getDriverType(SCGConnectionManager.java:208)
Solution
The first problem is that the analysis/conf files were corrupt or incorrect. To correct this issue, go into MWS and do the following:
Deploy Environment to File
Applications > Administration > System-Wide > Environments > Define Environments
Click on the “Deploy” action (Green Arrow)
Click on “Deploy To File” button
Save the “DeployedEnvironments.zip” file to local machine
Backup all files referenced within the zip file in the [saghome]/analysis/conf directory and sub-directories
Copy all files from the zip file to the [saghome]/analysis/conf directory
(NOTE: Be aware that there are two config directories in the zip file, the first directory is usually for analysis, the second is usually for dataCollector)
Upon starting Analytic Engine, we no longer received the Oracle error referencing “DISPLAY_NAME”
This was when we applied the following file fix.
Edit EndpointRegistry.xml
Edit the file: [saghome]/analysis/conf/system/EndpointRegistry.xml
The file will look as below.
<?xml version="1.0" encoding="UTF-8"?>
Edit the file, so that only the ‘Configuration Agent’ line is still in place. See the below example -
(NOTE: Ensure that the port numbers used match your particular installation)
<?xml version="1.0" encoding="UTF-8"?>
Start Analytic Engine
After modifying the file, start analytic engine.
If analytic engine does not start at this point there is another problem, if it does, then you must follow the step and redeploy the environment as follows:
Deploy Environment
Applications > Administration > System-Wide > Environments > Define Environments
Click on the “Deploy” action (Green Arrow)
Click on the “Deploy All” button
If all environments deploy successfully click the “Close” button
#webMethods-BPMS#webMethods#BPM