Resolving Problems with SAS Environment Manager Plugins

PostgreSQL Resources Not Configured Properly

After a PostgreSQL server is added into inventory, the Dashboard page indicates that the resource is not configured properly
On the Configuration Properties page for the server, specify this information:
postgresql.user
specify the Web Infrastructure Platform Data Server database user name. The default value is dbmsowner
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 postgres.exe or postgres.bat (on Windows). On UNIX, the path is /opt/sas/Lev1/SASWebInfrastructurePlatformDataServer/webinfdsvrc.sh. On W6X, the path is <SAS_Configuration_Directory>\Lev1\SASWebInfrastructurePlatformDataServer\webinfdsvrc.bat.

Tomcat Resources Not Configured Properly

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 .
  1. Open the file SAS_configuration_directory/Lev1/Web/SASEnvironmentManager/server-5.0.0-EE/hq-engine/hq-server/conf/hq-catalina.properties and find the jmx.url port number. The default value is 1099.
  2. On the Configuration Properties page for the server, specify the following property:
    jmx.url
    service:jmx.rmi:///jndi/rmi/://localhost:port_number

Cannot Discover tcServer Instances

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 startup 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 "&"

SAS Environment Manager Agent Will Not Start

Cannot start the SAS Environment Manager Agent by using the start script $SAS-configuration _directory/LevX/Web/SASEnvironmentManager/agent-5.0.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.0.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.
Copyright © SAS Institute Inc. All rights reserved.