Resolving Problems with SAS Environment Manager Plugins

After a PostgreSQL server is added into inventory, the Dashboard page indicates that the resource is not configured properly

In order to monitor this resource, you must provide PostgreSQL credentials in the resource definition. If you choose to not provide these credentials, the resource will not be monitored, but SAS Environment Manager will otherwise operate normally. The information that you specify depends on the type of PostgreSQL server that was added. If you choose to provide credentials, go to the Configuration Properties page for the server and specify this information:

postgresql.user

specify the user name for the PostgreSQL server. The user name that you specify differs, depending on the type of PostgreSQL server. Specify one of the following:

Web Infrastructure Platform Data Server

specify the Web Infrastructure Platform Data Server database user name. This user was created during installation. The default value is dbmsowner.

Job Monitor Data Server

specify the Job Monitor Data Server database user name. This user was created during installation. The default value is jmdbuser.

Data Remediation Data Server

specify the Data Remediation Data Server database user name. This user was created during installation. The default value is rmdbuser.

Data Management Data Server

specify the Data Management Data Server database user name. This user was created during installation. The default value is dmbdnadmin.

postgresql.pass

specify the password for the user name

postgresql.program

specify the path to the postgres.bat or postgres.sh file (on UNIX); or the postgres.exe or postgres.bat file (on Windows). The path that you specify depends on the type of PostgreSQL server. Specify one of the following values:.

Web Infrastructure Platform Data Server

/opt/sas/Lev1/SASWebInfrastructurePlatformDataServer/webinfdsvrc.sh (UNIX) or <SAS_Configuration_Directory>\Lev1\SASWebInfrastructurePlatformDataServer\webinfdsvrc.bat (Windows)

Job Monitor Data Server

/opt/sas/Lev1/JobMonitorDataServer/jobmntrdsvrc.sh (UNIX) or <SAS_Configuration_Directory>\Lev1\JobMonitorDataServer\jobmntrdsvrc.bat (Windows)

Data Remediation Data Server

/opt/sas/Lev1/DataRemediationDataServer/dmrmdtdsvrc.sh (UNIX) or <SAS_Configuration_Directory>\Lev1\DataRemediationDataServer\dmrmdtdsvrc.bat (Windows)

Data Management Data Server

/opt/sas/Lev1/DataManagementDataServer/dmdsvrc.sh (UNIX) or <SAS_Configuration_Directory>\Lev1\DataManagementDataServer\dmdsvrc.bat (Windows)

On the AIX platform, the Apache Tomcat 6.0 server Resource page displays the error

This resource is turned off or has
                  not been configured properly.  The problem is: Invalid configuration:
                  Error contacting resource: Can't connect to MBeanServer url

Open the file SAS_configuration_directory/Lev1/Web/SASEnvironmentManager/server-5.8.0-EE/hq-engine/hq-server/conf/hq-catalina.properties and find the jmx.url port number. The default value is 1099.
On the Configuration Properties page for the server, specify the following property:

jmx.url

service:jmx.rmi:///jndi/rmi/://localhost:port_number

On the H6I platform, no tcServer instances can be discovered.

HPUX has a limit of 1020 characters on command line queries. The parameters that the tcServer plugin uses to identify the tcServer process are not seen by the agent because they fall after the 1020 character limit has been reached. Edit the start-up script so that the parameters that the plugin needs are seen before the 1020 character limit.

Edit the catalina.sh script. Change this section of the script:

 eval \"$_RUNJAVA\" \"$LOGGING_CONFIG\" $JAVA_OPTS $CATALINA_OPTS \
     -Djava.endorsed.dirs=\"$JAVA_ENDORSED_DIRS\" -classpath \"$CLASSPATH\" \
     -Dcatalina.base=\"$CATALINA_BASE\" \
     -Dcatalina.home=\"$CATALINA_HOME\" \
     -Djava.io.tmpdir=\"$CATALINA_TMPDIR\" \
     org.apache.catalina.startup.Bootstrap "$@" start \
     >> "$CATALINA_OUT" 2>&1 "&"

Change the script to this:

 eval \"$_RUNJAVA\" \"$LOGGING_CONFIG\" \
     -Dcatalina.base=\"$CATALINA_BASE\" \
     -Dcatalina.home=\"$CATALINA_HOME\" \
     $JAVA_OPTS \
     $CATALINA_OPTS \
     -Djava.endorsed.dirs=\"$JAVA_ENDORSED_DIRS\" -classpath \"$CLASSPATH\" \
     -Djava.io.tmpdir=\"$CATALINA_TMPDIR\" \
     org.apache.catalina.startup.Bootstrap "$@" start \
     >> "$CATALINA_OUT" 2>&1 "&"

Cannot start the SAS Environment Manager Agent by using the start script

$SAS-configuration _directory/LevX/Web/SASEnvironmentManager/agent-5.8.0-EE/bin/hq-agent.sh
                  start

The console displays this message:

 Starting HQ Agent......Removed stale pid file:
 /local/install/cfgsas1/config/Lev1/Web/SASEnvironmentManager/agent-5.8.0-EE/wrapper/sbin
/../../wrapper/hq-agent.pid
 WARNING: HQ Agent may have failed to start.

Use the unset command to remove the COLUMNS environment variable.