config Command

[print|zip] config [CLAUSE];

• CLAUSEs provide additional information about the connection.

print config [ITEM] [full | !full] [output FILENAME];

• ITEM is

  oracleset user USERNAME password PASSWORD

• FILENAME is the name of the file to be created, and can include the PATH. If the FILENAME specified is “mxAudit.log”, it will append the data to the file that is generated by the configuration checker at server startup time. For example:

  print config output /app/rmi1050/logs/mxAudit.log;

To print information from the Oracle v$parameter view:

print config oracleset user system password manager;

The oracleset subcommand can be used to retrieve the Oracle compatibility mode setting and determine whether the optimizer mode is enabled. It also reports other settings that influence Server stability. For more information about v$parameter, refer to Oracle documentation.

The information returned represents what the kernel sees as it scans certain processes, and it can be used to verify that the application has been set up correctly without looking at the config files. The information is presented with the following headers:

**** Oracle Settings **** (if oracleset is specified)

This is a subset of the V$PARAMETERS table.

****ENOVIA Kernel JVM System Properties ****

This is a subset of Java system properties (System.getProperties)

**** ENOVIA Kernel Local Environment****

The 3DSpace kernel local environment shows the equivalent of typing Set on DOS or environ struct on UNIX.

**** ENOVIA Default Environment Settings****

This is a list of settings important to kernel loading and running, such as LD_LIBRARY_PATH and NLS_LANG.

**** ENOVIA Kernel Settings****

3DSpace kernel settings show output of Kernel INI in-memory values. There are name/value pairs determined by INI settings, environment variables, and the MatrixIniDefaults program. The name/value pairs listed in the print config output might have a "computed" value. For example, MX_CHARSET is used to determine whether the kernel needs to convert Java strings to the system character set. If MX_CHARSET is set to UTF8, no conversion is needed and the computed value that print config will print looks like:

MX_CHARSET=FALSE (if MX_CHARSET is set to UTF8 in the INI file)

****ENOVIA Jar Version****

This is the version of eMatrixServletRMI.jar (retrieved from matrix.util.Version.number ).

****Operating System Kernel Settings****

This shows operating system information, such as kernel process ID, os.name, os.arch, and os.version.

****ENOVIA Live Collaboration Upgrade Validation****

This is the output of the MQL Validate Upgrade command.

Below is an example of 3DSpace kernel JVM system properties that are output from the Print Config command:

2503 10/2/2003 4:56:43 PM ****eMatrix kernel JVM system properties***** 
2503 10/2/2003 4:56:43 PM java home: /usr/java/jdk1.3.1_06/jre 
2503 10/2/2003 4:56:43 PM java vm specification version: 1.0 
2503 10/2/2003 4:56:43 PM java vm specification vendor: Sun Microsystems Inc. 
2503 10/2/2003 4:56:43 PM java vm specification name: Java Virtual Machine Specification 
2503 10/2/2003 4:56:43 PM java vm version: 1.3.1_06-b01 
2503 10/2/2003 4:56:43 PM java vm vendor: Sun Microsystems Inc. 
2503 10/2/2003 4:56:43 PM java vm name: Java HotSpot(TM) Client VM 
2503 10/2/2003 4:56:43 PM java specification version: 1.3 
2503 10/2/2003 4:56:43 PM java specification vendor: Sun Microsystems Inc. 
2503 10/2/2003 4:56:43 PM java specification name: Java Platform API Specification
2503 10/2/2003 4:56:43 PM java class version: 47.0
2503 10/2/2003 4:56:43 PM java class path: /usr/java/jdk1.3.1_06/lib:/app/rmi1010/java/classes:/app/rmi1010/java/properties:/app/rmi1010/java/lib:/app/rmi1010/java/lib/ext:/app/rmi1010/java/custom:/usr/java/jdk1.3.1_06/lib/dt.jar:/usr/java/jdk1.3.1_06/lib/htmlconverter.jar:/usr/java/jdk1.3.1_06/lib/tools.jar:/app/rmi1010/java/lib/eMatrixServletRMI.jar:/app/rmi1010/java/lib/jdom.jar:/app/rmi1010/java/lib/xalan.jar:/app/rmi1010/java/lib/xerces.jar:/app/rmi1010/java/lib/common.jar:/app/rmi1010/java/lib/component.jar:/app/rmi1010/java/lib/domain.jar:/app/rmi1010/java/lib/engineering.jar:/app/rmi1010/java/lib/kcServlet.jar:/app/rmi1010/java/lib/xalanj1compat.jar

2503 10/2/2003 4:56:43 PM java version: 1.3.1_06 
2503 10/2/2003 4:56:43 PM java vendor: Sun Microsystems Inc. 
2503 10/2/2003 4:56:43 PM java vendor url: http://java.sun.com/ 
2503 10/2/2003 4:56:43 PM user name: dvlp 
2503 10/2/2003 4:56:43 PM user home: /home/dvlp 
2503 10/2/2003 4:56:43 PM user dir: /home/dvlp/buildCC/src/ematrix

zip config [output FILENAME];

• FILENAME is the fully qualified path and name of the file to be created.

For example:

zip config output /app/rmi1050/mxAudit.zip;

If the output clause is not included, a file named mxAudit.zip is created in the ENOVIA_INSTALL directory.

The zip file will contain the files referenced in the ENOVIA_INSTALL/mxAuditFile.txt, which is created at install time, as well as the mxAudit.log file that is created at server startup. Together the zipped up files provide a comprehensive picture of configuration settings.

Since the list of files in mxAuditFile.txt is a snapshot of what the configuration file locations were at install time, it is important to know what files are being included in the zip file. Administrators often change startup script names and locations. When the zip config command is issued, the command will generate the name of each file that is added to the zip file, enabling you to verify that the files being zipped are the current active files. Below is sample output from zip config:

****Begin eMatrix Zip Config**** 
zip config file : /app/rmi1050/logs/mxAudit.log 
zip config file : /app/rmi1050/scripts/mxEnv.sh 
zip config file : /app/rmi1050/java/properties/framework.properties 
zip config file : /opt/jakarta-tomcat-4.1.18/bin/catalina.sh