Download Administration Guide

HyperWorks Enterprise 11.1
Administration Guide
2
Administration Guide
Table of Contents
1
Introduction to Hyperworks Enterprise
3
Copyrights,
...................................................................................................................................
Trademarks, and Third Party Licenses
5
System
...................................................................................................................................
Requirements
6
Supported
...................................................................................................................................
Platforms
7
2
HWE Portal Service on Windows
9
Starting
...................................................................................................................................
HWE
10
Stopping
...................................................................................................................................
HWE
11
Restarting
...................................................................................................................................
HWE
12
3
HWE Portal Service On Linux
13
Starting
...................................................................................................................................
HWE
14
Stopping
...................................................................................................................................
HWE
15
Restarting
...................................................................................................................................
HWE
16
Determining
...................................................................................................................................
Installation Location of HWE
17
Determining
...................................................................................................................................
if HWE is Installed & Running
18
4
Advanced Configuration
19
Configuring
...................................................................................................................................
Access Management Service
20
Configuring
...................................................................................................................................
Administrative Users
25
Configuring
...................................................................................................................................
File Operations Performance
26
Configuring
...................................................................................................................................
JVM Performance
28
Enabling
...................................................................................................................................
SSL for HWE on Linux
29
Configuring
...................................................................................................................................
the Postgres Database
32
Configuring
...................................................................................................................................
HWE logging
34
Configuring
...................................................................................................................................
Session Timeout
36
Configuring
...................................................................................................................................
the HWE License Server
38
Configuring
...................................................................................................................................
HWE Language/Localization
40
5
Location of HWE Files
42
6
Database Field Lengths
44
Copyright © 1992 - 2012 Altair Engineering Inc.
Introduction to Hyperworks Enterprise
1
3
Introduction to Hyperworks Enterprise
HyperWorks Enterprise (HWE) is a modern Service Oriented Architecture coupled with the market
leading HPC workload management and job scheduling solution - PBS Professional® , constituting the
foundation of Altair's HPC offering. HyperWorks Enterprise increases high-performance computing
productivity, providing users with a reliable and affordable enterprise simulation platform.
Benefits:
Users First
HyperWorks Enterprise Solutions are the most natural way to organize, automate and manage
the contents used throughout the simulation life cycle, working in an extremely intuitive and userfriendly Web-based interface.
Data Freshness
With HyperWorks Enterprise Solutions, users can immediately begin managing their personal
data or collaborating in small teams, without the overhead typical of enterprise data management
and PLM systems, maintaining the content pedigree and synchronizing data in nearly real time.
Human Centric
HyperWorks Enterprise Solutions provide users with an enjoyable data and process management
experience, employing software and hardware resources to streamline complex analysis with a
few mouse clicks.
Components available through the installation of HyperWorks Enterprise (for more information about
HyperWorks Enterprise see the HyperWorks Enterprise Administration Guide, which can be
downloaded from the HyperWorks or PBSWorks documentation user area):
Compute Manager which includes:
Compute Manager application and services
Results Visualization plug-in (use of the plug-in requires Results Visualization Service to be
installed.)
Access Management Service
Results Visualization Service
Compute Manager
Compute Manage is a job submission and monitoring portal which enables users to run, monitor and
manage workloads on distributed resources remotely. Compute Manager uses the High Performance
Computing workload management capability of Altair’s PBS Application Services and PBS Professional
for efficient resource utilization, access to the cloud for job submission and subsequent accounting.
Copyright © 1992 - 2012 Altair Engineering Inc.
4
Administration Guide
Results Visualization Service
Results Visualization provides necessary features and functionalities to access, process and visualize
CAE results information through an easy and intuitive graphical user interface, embedded directly into
the web browser. This allows users to access these features anytime and from anywhere without the
need for installing any post processing applications on their desktop. In the current release, these
features are accessible through the HyperWorks Enterprise Compute Manager web interface.
Access Management Service
Access Management Service provides a toolkit for managing users and groups, as well as access
control policies. For more information about Access Management Service, you may download the
Access Management Service Administrator's Toolkit Command Reference Guide from the HyperWorks
or PBSWorks documentation user area.
Compute Manager and Results Visualization Service must be installed separately. The Results
Visualization Service must be installed to use the plug-in with Compute Manager. For more information
about Compute Manager see the Compute Manager Installation and Administration Guide. For more
information about Results Visualization Service see the Results Visualization Service Installation and
Administration Guide. Both documents can be downloaded from the HyperWorks or PBSWorks
documentation user area.
Copyright © 1992 - 2012 Altair Engineering Inc.
Introduction to Hyperworks Enterprise
1.1
5
Copyrights, Trademarks, and Third Party Licenses
HyperWorks Enterprise Administration Guide 11.1, Updated: 8/31/2012.
Copyright© 2003-2012 Altair Engineering, Inc. All Rights Reserved
HWE Compute Manager, HyperWorks Enterprise, PBS™, PBS Works™, PBS GridWorks®, PBS
Professional®, PBS Analytics™, PBS Desktop™, PBS Portal™, PBS Animate™, PBS BioChem™,
PBS MCAE™, e-BioChem™, e-Compute™ and e-Render™ are trademarks of Altair Engineering, Inc.
and are protected under U.S. and international laws and treaties.
All other marks are the property of their respective owners.
Copyright notice does not imply publication. Contains trade secrets of Altair Engineering, Inc.
Decompilation or disassembly of this software is strictly prohibited.
Copyright © 1992 - 2012 Altair Engineering Inc.
6
1.2
Administration Guide
System Requirements
Minimum Hardware Requirements for Compute Manager
Hardware
Minimum
Requirement
Recommended
CPU
1 CPU
2 CPU
Memory
(Physical)
2 GB
8 GB
Disk Space
20 GB
50 GB
Minimum Hardware Requirements for Results Visualization Service
Hardware
Minimum
Requirement
Recommended
CPU
2 CPU
4 CPU
Memory
(Physical)
8 GB
12 GB
Disk Space
50 GB
100 GB
Resources are specific to the server that Results Visualization Service is running on.
Minimum System Requirements
On Linux systems, the Open SSH daemon using the SSH2 protocol is required.
Assumptions, Constraints, and Dependencies
In order to register a user session of Compute Manager to an Enterprise PBS Professional complex,
the complex head node must be running PBS Professional 10.4 or later, and PBS Application Services
11.0.1 or later. Please contact your site administrator for further information.
Copyright © 1992 - 2012 Altair Engineering Inc.
Introduction to Hyperworks Enterprise
1.3
7
Supported Platforms
HyperWorks Enterprise is supported on the following platforms:
Windows 64bit
Windows Server 2008
Windows Server 2008 R2
Linux 64bit
Suse Linux Enterprise Server 10 & 11
Red Hat Enterprise Linux 5 & 6
Cent OS 5.5
Supported Browsers
Windows
Firefox v4.x - v13 (preferred)
Google Chrome 12 - 20 (preferred)
Internet Explorer v8 - v9 (limited)
Linux
Firefox v4.x - v14 (preferred)
Google Chrome 15 - 21 (preferred)
OSX
Safari 5 - 6 (currently not heavily tested)
Google Chrome Frame plug-in
Compute Manager
Internet Explorer versions 8 and 9 do not natively support the multi-file upload mechanisms for local files
nor the file upload progress meter in Compute Manager. It has been observed that many times
installing the Chromium projects Google Chrome Frame plug-in on Windows XP, Vista and Windows 7
has provided indirect support for this. However, this configuration has not formally been tested, so it is
not fully supported by Altair. Please use the Chromium projects at your own discretion.
Results Visualization Service
It is observed that installing Google Chrome Frame on IE 8 and 9 significantly improves the
performance of Results Visualization, especially plotting use cases. However, the plug-in appears to
Copyright © 1992 - 2012 Altair Engineering Inc.
8
Administration Guide
have some random issues with the Hyperview Player plug-in, which sometimes leads to unexpected
behavior during animation data viewing. In these instances, the generated animation file (h3d) can be
downloaded and viewed locally using the standalone version of HyperView player. This configuration
(Google Chrome Frame + IE 8/9) has not been formally tested, so it is not fully supported by Altair. If
issues arise, it may be recommended to uninstall the plug-in.
To install and configure Google Chrome Frame see the Compute Manager Installation and
Administration Guide, which can be downloaded from the HyperWorks or PBSWorks documentation
user area.
Copyright © 1992 - 2012 Altair Engineering Inc.
HWE Portal Service on Windows
2
HWE Portal Service on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
9
10
2.1
Administration Guide
Starting HWE
To start HWE:
1. Open Control Panel->Administrative Tools->Services
2. Right click on "HWE Portal Service" and click the "Start" option.
Copyright © 1992 - 2012 Altair Engineering Inc.
HWE Portal Service on Windows
2.2
Stopping HWE
To stop HWE:
1. Open Control Panel->Administrative Tools->Services
2. Right click on "HWE Portal Service" and click the "Stop" option.
Copyright © 1992 - 2012 Altair Engineering Inc.
11
12
2.3
Administration Guide
Restarting HWE
To restart HWE:
1. Open Control Panel->Administrative Tools->Services
2. Right click on "HWE Portal Service" and click the "Restart" option.
Copyright © 1992 - 2012 Altair Engineering Inc.
HWE Portal Service On Linux
3
HWE Portal Service On Linux
Copyright © 1992 - 2012 Altair Engineering Inc.
13
14
3.1
Administration Guide
Starting HWE
To start HWE:
1. At the Linux command line prompt enter:
/etc/init.d/hweportal start
The following messages will be displayed:
Starting Postgres server
sudo -u user1 /opt/altair/hwe/11.1/scripts/startpostgres.sh /opt/
altair/hwe/11.1/thirdparty/postgres
waiting for server to start.....LOG: database system was shut down at
2012-08-11 09:39:35 EDT
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
done
server started
Postgres server started, pid: 19832
[OK]
Starting HWE Portal Server
Platform : x86_64
64 Bit machine
Using CATALINA_BASE:
/opt/altair/hwe/11.1/thirdparty/apache/tomcat
Using CATALINA_HOME:
/opt/altair/hwe/11.1/thirdparty/apache/tomcat
Using CATALINA_TMPDIR: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/
temp
Using JRE_HOME:
/opt/altair/hwe/11.1/thirdparty/java
Using CLASSPATH:
/opt/altair/hwe/11.1/thirdparty/apache/tomcat/
bin/bootstrap.jar
HWE Portal Server started, pid: 19875
You can access the portal using link http://hwesuse113-01.prog.altair.
com:8086/hwe
[OK]
Copyright © 1992 - 2012 Altair Engineering Inc.
HWE Portal Service On Linux
3.2
Stopping HWE
To stop HWE:
1. At the Linux command line prompt enter:
/etc/init.d/hweportal stop
The following message will be displayed:
Stopping HWE Portal Server PID 17295:
Stopping Postgres server PID 17249
Copyright © 1992 - 2012 Altair Engineering Inc.
[OK]
[OK]
15
16
3.3
Administration Guide
Restarting HWE
To restart HWE:
1. At the Linux command line prompt enter:
/etc/init.d/hweportal restart
The following messages will be displayed:
Restarting HWE Portal Server
Stopping HWE Portal Server PID 19875: LOG: unexpected EOF on client
connection
[OK]
LOG: received smart shutdown request
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
Stopping Postgres server PID 19832
[OK]
Starting Postgres server
sudo -u user1 /opt/altair/hwe/11.1/scripts/startpostgres.sh /opt/
altair/hwe/11.1/thirdparty/postgres
waiting for server to start....LOG: database system was shut down at
2012-08-11 09:40:51 EDT
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
done
server started
Postgres server started, pid: 20104
[OK]
Starting HWE Portal Server
Platform : x86_64
64 Bit machine
Using CATALINA_BASE:
/opt/altair/hwe/11.1/thirdparty/apache/tomcat
Using CATALINA_HOME:
/opt/altair/hwe/11.1/thirdparty/apache/tomcat
Using CATALINA_TMPDIR: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/
temp
Using JRE_HOME:
/opt/altair/hwe/11.1/thirdparty/java
Using CLASSPATH:
/opt/altair/hwe/11.1/thirdparty/apache/tomcat/
bin/bootstrap.jar
HWE Portal Server started, pid: 20147
You can access the portal using link http://hwesuse113-01.prog.altair.
com:8086/hwe
[OK]
Copyright © 1992 - 2012 Altair Engineering Inc.
HWE Portal Service On Linux
3.4
Determining Installation Location of HWE
To determine the installation location of HWE:
1. At the Linux command line prompt enter:
cat /etc/hweportal.conf
The installation location is identified by SERVER_HOME:
SERVER_HOME=/opt/altair/hwe/11.1
Copyright © 1992 - 2012 Altair Engineering Inc.
17
18
3.5
Administration Guide
Determining if HWE is Installed & Running
To check that HWE is running:
1. At the Linux command line prompt enter:
/etc/init.d/hweportal status
If HWE is running the following message will be displayed:
HWE Portal Server (pid 20147) is running
You can access the portal using link http://hwesuse113-01.prog.altair.
com:8086/hwe
2. To get more information about the status of HWE, enter the following command at the Linux
command line prompt:
ps -ef | grep hwe
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
4
Advanced Configuration
Copyright © 1992 - 2012 Altair Engineering Inc.
19
20
4.1
Administration Guide
Configuring Access Management Service
During installation, HWE can be configured to use either Windows based or SSH based authentication.
This authentication information is stored in the file AA_jaas.config. The location of the file for a
typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1\config\AAServiceHome\config
on Linux
: /opt/altair/hwe/11.1/config/AAServiceHome/config
HWE supports the following methods for authentication:
Using a Datastore
Using NIS
Using PAM
Using SSH
Using Windows
Please note that PAM and NIS have not been fully tested, therefore use of these authentication
methods should be used with caution.
Sample configuration files for all authentication methods are stored in the sample config files
directory. Administrators can use these configuration files for:
Changing the authentication from one method to another
Changing the Datastore
Changing the NIS server
Changing the SSH server
AA_jaas.config.ds file
LoginModule {
com.altair.jaas.module.DatastoreLoginModule Required
java.naming.security.authentication="simple"
debug="true";
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Super_User_Login {
com.altair.jaas.module.DatastoreLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
21
AA_jaas.config.nis file
LoginModule {
com.sun.security.auth.module.JndiLoginModule Required
strongDebug="false"
user.provider.url="$HWE_AA_NIS_USER_URL$"
group.provider.url="$HWE_AA_NIS_GROUP_URL$"
tryFirstPass="false"
useFirstPass="false"
storePass="true"
clearPass="true"
debug="true"
java.naming.factory.initial=com.sun.jndi.nis.NISCtxFactory;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Super_User_Login {
com.altair.jaas.module.DatastoreLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
AA_jaas.config.pam file
LoginModule {
ch.odi.jaaspam.PamLoginModule Sufficient service=login;
com.altair.jaas.module.DatastoreLoginModule Sufficient;
};
AA_jaas.config.ssh file
LoginModule {
com.altair.jaas.module.SSHUnixLoginModule Required
host="$HWE_AA_SSH_SERVER$"
cache_ttl="60";
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Super_User_Login {
com.altair.jaas.module.DatastoreLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
AA_jaas.config.win file
LoginModule {
com.altair.jaas.module.ProcessRunnerWindowsLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Super_User_Login {
com.altair.jaas.module.DatastoreLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Copyright © 1992 - 2012 Altair Engineering Inc.
22
Administration Guide
Changing authentication to a Datastore
1. Back up the existing AA_jaas.config.
2. Copy the sample configuration file AA_jaas.config.ds to AA_jaas.config.
3. Update the Datastore by following the instructions for Changing the Datastore.
Changing authentication to NIS
1. Back up the existing AA_jaas.config.
2. Copy the sample configuration file AA_jaas.config.nis to AA_jaas.config.
3. Update the NIS server by following the instructions for Changing the NIS Server.
Changing authentication to SSH
1. Back up the existing AA_jaas.config.
2. Copy the sample configuration file AA_jaas.config.ssh to AA_jaas.config.
3. Update the SSH server by following the instructions for Changing the SSH Server.
Changing authentication to PAM
1. Back up the existing AA_jaas.config.
2. Copy the sample configuration file AA_jaas.config.pam to AA_jaas.config.
3. The HWE server will need to be restarted for the changes to be reflected.
Restart the HWE server on Linux
Restart the HWE server on Windows
Changing authentication to Windows
1. Back up the existing AA_jaas.config.
2. Copy the sample configuration file AA_jaas.config.win to AA_jaas.config.
3. The HWE server will need to be restarted for the changes to be reflected.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
23
Changing the SSH server
1. Edit the AA_jaas.config file to change the SSH server that will be used to authenticate HWE
users. Replace $HWE_AA_SSH_SERVER$ with the new SSH server IP address or hostname.
LoginModule {
com.altair.jaas.module.SSHUnixLoginModule Required
host="$HWE_AA_SSH_SERVER$"
cache_ttl="60";
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Super_User_Login {
com.altair.jaas.module.DatastoreLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
2. The HWE server will need to be restarted for the changes to be reflected after updating the SSH
server.
Restart the HWE server on Linux
Restart the HWE server on Windows
Changing the Datastore
1. Edit the Datastore.properties file to configure the datastore. The location of the file for a
typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1
\config\AAServiceHome\config\Datastore
on Linux
: /opt/altair/hwe/11.1/config/AAServiceHome/config/Datastore
Replace all variables denoted by $datastorePropertyName$ with the appropriate Datastore property
values.
java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
com.altair.aaservice.ldap.url=$HWE_AA_DOMAIN_URL$
com.altair.aaservice.ldap.domain=$HWE_AA_DOMAIN_COMPONENT$
com.altair.aaservice.ldap.domaincomponent=$HWE_AA_DOMAIN_COMPONENT_SPLIT$
com.altair.aaservice.ldap.matchOnUserDN=$HWE_AA_LDAP_MATCHONUSERDN$
com.altair.aaservice.ldap.principalDNPrefix=$HWE_AA_LDAP_PRINCIPALDNPREFIX$
com.altair.aaservice.ldap.uidAttrName=$HWE_AA_LDAP_UIDATTRNAME$
com.altair.aaservice.ldap.roleAttributeID=$HWE_AA_LDAP_ROLEATTRIBUTEID$
com.altair.aaservice.ldap.commanNameAttributeId=$HWE_AA_LDAP_CNATTRIBUTEID$
com.altair.aaservice.ldap.searchscope=$HWE_AA_LDAP_SEARCHSCOPE$
com.altair.aaservice.ldap.firstNameID=$HWE_AA_LDAP_GIVENNAME$
com.altair.aaservice.ldap.lastNameID=$HWE_AA_LDAP_LASTNAMEID$
com.altair.aaservice.ldap.emaiId=$HWE_AA_LDAP_EMAILID$
com.altair.aaservice.ldap.departmentId=$HWE_AA_LDAP_DEPTID$
com.altair.aaservice.ldap.TelephoneNoId=$HWE_AA_LDAP_PHONEID$
com.altair.aaservice.ldap.TitleId=$HWE_AA_LDAP_TITLEID$
com.altair.aaservice.ldap.LocationId=$HWE_AA_LDAP_LOCATIONID$
com.altair.aaservice.ldap.CountryId=$HWE_AA_LDAP_COUNTRYID$
com.altair.aaservice.ldap.ManagerId=$HWE_AA_LDAP_MANAGERID$
com.altair.aaservice.ldap.domainuser.id=$HWE_AA_LDAP_DOMUSERID$
com.altair.aaservice.ldap.domainuser.password=$HWE_AA_LDAP_DOMPASSWORD$
Copyright © 1992 - 2012 Altair Engineering Inc.
24
Administration Guide
2. The HWE server will need to be restarted for the changes to be reflected after updating the Datastore
information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Changing the NIS server
1. Edit the AA_jaas.config file to change the NIS user and group URL by replacing
$HWE_AA_NIS_USER_URL$ and $HWE_AA_NIS_GROUP_URL$ with the appropriate values. For
example:
user.provider.url="nis://NISServerHostName/NISDomain/user"
group.provider.url="nis://NISServerHostName/NISDomain/system/group"
LoginModule {
com.sun.security.auth.module.JndiLoginModule Required
strongDebug="false"
user.provider.url="$HWE_AA_NIS_USER_URL$"
group.provider.url="$HWE_AA_NIS_GROUP_URL$"
tryFirstPass="false"
useFirstPass="false"
storePass="true"
clearPass="true"
debug="true"
java.naming.factory.initial=com.sun.jndi.nis.NISCtxFactory;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
Super_User_Login {
com.altair.jaas.module.DatastoreLoginModule Required;
com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/
};
2. The HWE server will need to be restarted for the changes to be reflected after updating the NIS
server.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
4.2
25
Configuring Administrative Users
During the installation of HWE, the installation process prompts for a userid and password that will be
used to administer the HWE portal. The installation process adds this administrator to a group called
"altairadmin". To add or remove HWE portal administrators, simply add or remove users from this
group using Access Management Service (AMS). As of the HWE 11.1 release, an AMS tool kit is
available to manage users and groups. For more information about AMS see the Access Management
Service Administrator's Toolkit Command Reference Guide, which can be downloaded from the
HyperWorks or PBSWorks documentation user area.
Copyright © 1992 - 2012 Altair Engineering Inc.
26
4.3
Administration Guide
Configuring File Operations Performance
When a job is running and a user wants to view or download a file from the execution directory of the
job, HWE asks PBS Application Services (PAS) for the contents of the file in chunks. By default, HWE
asks for 8 MB of content at a time, therefore a 100 MB file results in 100/8 number of calls to PAS.
To improve the performance, this default can be set to a higher value (16, 32, 64. etc.). For instance,
increasing the default from 8 MB to 16 MB, halves the number of calls to PAS.
This default is stored in a script file called server-start.sh on Linux and InstallHWEService.
bat on Windows. The location of this file for a typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1\scripts
on Linux
: /opt/altair/hwe/11.1/scripts
The argument that needs to be modified is the JVM argument -DAIF_FILECHUNK_SIZE_MB.
server-start.sh file
This is the area of the file that will need to be modified (this file is too large to show in its entirety):
#Set product specific parameters
HWE_INSTALLATION_DIRECTORY="${PRODUCT_HOME}"
JAVA_OPTS="-DHWE_INSTALLATION_DIRECTORY=$HWE_INSTALLATION_DIRECTORY"
JAVA_OPTS="$JAVA_OPTS -DAIF_WSDL_LOCATION=file:///$HWE_INSTALLATION_DIRECTORY/services/cm/config/wsdl/"
JAVA_OPTS="$JAVA_OPTS -DAIF_FILECHUNK_SIZE_MB=8"
#JAVA_OPTS="$JAVA_OPTS -Dderby.system.home=$HWE_INSTALLATION_DIRECTORY/binaries/framework/data/datastore"
#JAVA_OPTS="$JAVA_OPTS -Dderby.infolog.append=true"
JAVA_OPTS="$JAVA_OPTS -DAA_CONFIG_DIR=$HWE_INSTALLATION_DIRECTORY/config/AA"
JAVA_OPTS="$JAVA_OPTS -DAA_SERVICE_HOME=$HWE_INSTALLATION_DIRECTORY/config/AAServiceHome"
JAVA_OPTS="$JAVA_OPTS -DAA_CONFIG_DIR=$HWE_INSTALLATION_DIRECTORY/config/AA"
JAVA_OPTS="$JAVA_OPTS -DAA_BIN_DIR=$HWE_INSTALLATION_DIRECTORY/binaries/native"
JAVA_OPTS="$JAVA_OPTS -DAA_SERVICE_HOME=$HWE_INSTALLATION_DIRECTORY/config/AAServiceHome"
export JAVA_OPTS
InstallHWEService.bat file
This is the area of the file that will need to be modified (this file is too large to show in its entirety):
rem Set extra parameters
"%EXECUTABLE%" //US//%SERVICE_NAME% --Environment "HWE_INSTALLATION_DIRECTORY=%
HWE_INSTALLATION_DIRECTORY%" --JvmOptions "-Xmx1024m;-Djava.security.auth.login.
config=%HWE_INSTALLATION_DIRECTORY%/config/login.config;DHWE_INSTALLATION_DIRECTORY=%HWE_INSTALLATION_DIRECTORY%;DAIF_WSDL_LOCATION="file:///"%HWE_INSTALLATION_DIRECTORY%"/services/cm/config/
wsdl/";-Dderby.system.home=%HWE_INSTALLATION_DIRECTORY%/binaries/framework/data/
datastore;-Dderby.infolog.append=true;-Djava.protocol.handler.pkgs=com.altair.
common.filetransfer;-DAA_CONFIG_DIR=%HWE_INSTALLATION_DIRECTORY%/config/AA;DAA_BIN_DIR=%HWE_INSTALLATION_DIRECTORY%/binaries/native;-DAA_SERVICE_HOME=%
HWE_INSTALLATION_DIRECTORY%/config/AAServiceHome;-Dcatalina.base=%CATALINA_BASE%;Dcatalina.home=%CATALINA_HOME%;-Djava.endorsed.dirs=%CATALINA_HOME%\endorsed;DAIF_FILECHUNK_SIZE_MB=8" --StartMode jvm --StopMode jvm
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
27
Increasing the value of the JVM argument -DAIF_FILECHUNK_SIZE_MB improves performance,
however, this has an adverse affect on memory (RAM required). If this value is set to 32 MB and 10
users are simultaneously downloading the file, potentially 32*10 MB of RAM could be required just for
downloads. This can result in an OutOfMemory exception, therefore take careful consideration when
determining the optimal value for this argument.
The HWE server will need to be restarted for the changes to be reflected after updating the JVM
argument -DAIF_FILECHUNK_SIZE_MB:
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
28
4.4
Administration Guide
Configuring JVM Performance
To sustain a large number of concurrent users (over 30), the Java Virtual Machine (JVM) heap size
may need to be adjusted. Currently, the default JVM heap size is 1024 MB. If OutOfMemory errors or
warnings are reported in the CM log files, this value should be increased. It can be increased in
multiples of 256 MB.
Thie Java heap size default is stored in a script file called server-start.sh on Linux and
hweportal.bat on Windows. The location of this file for a typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1\scripts
on Linux
: /opt/altair/hwe/11.1/scripts
The JVM argument that needs to be modified is the -Xmx1024m argument. Increase the "1024" value.
server-start.sh file
This is the area of the file that will need to be modified (this file is too large to show in its entirety):
CATALINA_OPTS="-Xmx1024m -D${prodid}"
CATALINA_OPTS="$CATALINA_OPTS -Djava.security.auth.login.config=$HWE_INSTALLATION_DIRECTORY/config/login.co
CATALINA_OPTS="$CATALINA_OPTS -Djava.protocol.handler.pkgs=com.altair.common.filetransfer"
export CATALINA_OPTS
hweportal.bat file
This is the area of the file that will need to be modified (this file is too large to show in its entirety):
set CATALINA_OPTS= "-Xmx1024m"
set CATALINA_OPTS="-Djava.security.auth.login.config=%HWE_INSTALLATION_DIRECTORY%/
config/login.config"
set CATALINA_HOME=%TOMCAT_HOME%
The HWE server will need to be restarted for the changes to be reflected after updating the JVM
argument -Xmx1024m
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
4.5
29
Enabling SSL for HWE on Linux
Enabling SSL for HWE on Linux requires root privileges.
The HWE installation directory will be denoted by <HWE_INSTALL_DIR>. The installation directory for
a typical installation of HWE on Linux is:
on Linux
: /opt/altair/hwe/11.1/
1. Determine if the environment variable JAVA_HOME is set properly by entering the following at the
Linux command line prompt:
echo $JAVA_HOME
JAVA_HOME should be set to <HWE_INSTALL_DIR>/thirdparty/java.
If it is not then enter the following command:
export JAVA_HOME=<HWE_INSTALL_DIR>/11.1/thirdparty/java
2. Create a Tomcat Certificate Keystore File by running the following command:
$JAVA_HOME/bin/keytool -keystore <HWE_INSTALL_DIR>/thirdparty/apache/tomcat/conf/keystore -genkey -alias
After executing this command, you will first be prompted for the keystore password. The default
password used by Tomcat is "changeit" (all lower case), although you can specify a custom
password if you like. You will also need to specify the custom password in the server.xml
configuration file, as described in step 3.
Next, you will be prompted for general information about this Certificate, such as company, contact
name, and so on. This information will be displayed to users who attempt to access a secure page in
your application, so make sure that the information provided here matches what they will expect.
Finally, you will be prompted for the key password, which is the password specifically for this
Certificate (as opposed to any other Certificates stored in the same keystore file). You MUST use
the same password here as was used for the keystore password itself. This is a restriction of the
Tomcat implementation. (Currently, the keytool prompt will tell you that pressing the ENTER key does
this for you automatically.)
If everything was successful, you now have a keystore file in the <HWE_INSTALL_DIR>/
thirdparty/apache/tomcat/conf directory with a Certificate that can be used by your server.
Copyright © 1992 - 2012 Altair Engineering Inc.
30
Administration Guide
3. Edit the Tomcat Configuration file <HWE_INSTALL_DIR>/thirdparty/apache/tomcat/conf/
server.xml
Paste the following block of code
<Connector
port="8443" maxThreads="200"
scheme="https" secure="true" SSLEnabled="true"
connectionTimeout="20000"
clientAuth="false" sslProtocol="TLS"
keystoreFile="<HWE_INSTALL_DIR>/thirdparty/apache/tomcat/conf/keystore"
keyAlias="tomcat" keystorePass="passwordFromStep2"/>
After the following block of code:
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS" />
The keystorePass= should be the password used during step 2.
4. Create a backup of the Tomcat web application configuration file <HWE_INSTALL_DIR>/
thirdparty/apache/tomcat/conf/web.xml.
5. Edit the Tomcat web application configuration file to set up redirection from http://
hostname:8086/hwe to https://hostname:8443/hwe:
Paste the following block of code
<security-constraint>
<web-resource-collection>
<web-resource-name>Entire Application</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
After the following block of code:
<session-config>
<session-timeout>30</session-timeout>
</session-config>
HWE runs as a normal user (hweuser). The hweuser does not have permission to use privileged
ports (443), therefore a non-privileged port (8443) is used.
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
31
6. The HWE server will need to be restarted for the changes to be reflected:
Restart the HWE server on Linux
Restart the HWE server on Windows
7. Accept the Certificate:
From a web browser, navigate to https://<hostname>:8443 and accept the certificate when
you are prompted by the browser.
Copyright © 1992 - 2012 Altair Engineering Inc.
32
4.6
Administration Guide
Configuring the Postgres Database
HWE uses Postgres 8.3 which is bundled with the HWE installer. HWE can be changed to point to a
different Postgres database by updating the context.xml file. The location of the file for a typical
installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1
\thirdparty\apache\tomcat\conf
on Linux
: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/conf
context.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!-Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--><!-- The contents of this file will be loaded for each web application --><Context>
<!-- Default set of monitored resources -->
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<Loader className='com.altair.awpf.classloader.AWPFWebappLoader' />
<Manager pathname="" />
<!-- Uncomment this to enable Comet connection tacking (provides events
on session expiration as well as webapp lifecycle) -->
<!-<Valve className="org.apache.catalina.valves.CometConnectionManagerValve" />
-->
<Resource auth="Container" driverClassName="org.postgresql.Driver" maxActive="20" maxIdle="10" maxWait=
password="user1" type="javax.sql.DataSource" url="jdbc:postgresql://localhost:6767/hwewebportal" user
</Context>
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
33
Configuring the Postgres database
The default entry in context.xml that points to the HWE database is shown below:
<Resource auth="Container" driverClassName="org.postgresql.Driver" maxActive="20" maxIdle="10" maxWait="-1"
password="user1" type="javax.sql.DataSource" url="jdbc:postgresql://localhost:6767/hwewebportal" usernam
1. To configure HWE to point to a different Postgres database, edit the context.xml file and
change the resource definitions for the datastore where:
POSTGRES_SERVER_HOST is the hostname or IP address of the host where Postgres is
installed.
POSTGRES_SERVER_PORT is the Port configured for Postgres.
POSTGRES_DB_NAME is the Postgres database name.
POSTGRES_DB_USER is the Postgres user name which HWE Manager will use to connect
to the database.
POSTHRES_DB_PASSWORD is the Password for the Postgres user name.
<Resource auth="Container" driverClassName="org.postgresql.Driver" maxActive="20" maxIdle="10" maxWai
password="POSTHRES_DB_PASSWORD" type="javax.sql.DataSource"
url="jdbc:postgresql://POSTGRES_SERVER_HOST:POSTGRES_SERVER_PORT/POSTGRES_DB_NAME"
username="POSTGRES_DB_USER"/>
2. The HWE server will need to be restarted for the changes to be reflected after updating the
logging information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
34
4.7
Administration Guide
Configuring HWE logging
The HWE logging behavior can be defined in the file log4j.properties.
for a typical installation of HWE is:
The location of the file
on Windows : C:\Program Files\altair\hwe\11.1\config
on Linux
: /opt/altair/hwe/11.1/config
By default, HWE logs at an "INFO" level and keeps a maximum of two (2) files as backup.
log4j.properties file:
log4j.appender.frameworkRollingFile=org.apache.log4j.RollingFileAppender
log4j.appender.frameworkRollingFile.File=awpflog.log
log4j.appender.frameworkRollingFile.MaxFileSize=2MB
log4j.appender.frameworkRollingFile.MaxBackupIndex=2
log4j.appender.frameworkRollingFile.layout=org.apache.log4j.PatternLayout
log4j.appender.frameworkRollingFile.layout.ConversionPattern= %n%p, %d{dd MMM yyy HH:mm:ss,SSS} -{%F: %L} log4j.rootLogger=INFO, frameworkRollingFile
Configuring logging behavior
1. You can define the level of logging by editing the log4j.properties file and setting the
parameter log4j.rootLogger to one of the following values:
OFF - designated the highest possible ranking and is intended to turn off logging
FATAL - designates very severe error events that will presumably lead the application to abort
ERROR - designates error events that might still allow the application to continue running
WARN - designates potentially harmful situations
INFO - designates informational messages that highlight the progress of the application at coarsegrained level
DEBUG - designates fine-grained informational events that are most useful to debug an application
TRACE - designates finer-grained informational events than the DEBUG
ALL - designates the lowest possible rank and is intended to turn on all logging
log4j.rootLogger=INFO, frameworkRollingFile
2. The HWE server will need to be restarted for the changes to be reflected after updating the
logging information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
35
Configuring log file size and number of backups
1. You can define the maximum file size and the number of backup files by editing the log4j.
properties file and setting the MaxFileSize and MaxBackupIndex parameters:
log4j.appender.frameworkRollingFile.MaxFileSize=2MB
log4j.appender.frameworkRollingFile.MaxBackupIndex=2
2. The HWE server will need to be restarted for the changes to be reflected after updating the
logging information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
36
4.8
Administration Guide
Configuring Session Timeout
To change the session timeout for HWE, modify the the HWE platform configuration file, platform.xml.
The location of this file for a typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1\config
on Linux
: /opt/altair/hwe/11.1/config
platform.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!-A sample configuration for AWPF platform This configuration is
supposed to have various settings whic hare common for various
application spresent in the system.
All other application can derive application settings from here as derived configuration
-->
<awpplatform version="17.6.2" buildnumber="101220100800">
<customer>
<name>Altair</name>
<description>Altair Engineering</description>
<logouri>../login/resources/images/vendor/HyperWorks_logo.png</logouri>
<custombranding>
<![CDATA[<div class="customer-branding">HTML HERE</div>]]>
</custombranding>
</customer>
<copyright>LABEL_COPYRIGHT</copyright>
<contexlisteners>
<listener-class>com.altair.awpf.services.notification.core.NotificationDispatcherTimerTask<
</contexlisteners>
<notification>
<dispatcher-interval>1000</dispatcher-interval>
</notification>
<preference>
<!--<preserver>com.altair.awpf.services.preferences.core.DBPreserveAndRestore</preserver>-<preserver>com.altair.awpf.services.preferences.core.FilePreserveAndRestore</preserver>
</preference>
<eventregistration>
<platformevnet>
<listener>com.altair.awpf.services.notification.core.NotificationManagerEventListen
<listener>com.altair.awpf.services.preferences.core.SettingManagerEventListener</li
</platformevnet>
<applicationevent>
</applicationevent>
</eventregistration>
<!-- tab close check time interval in seconds -->
<disconnectCheckInterval>3600</disconnectCheckInterval>
<generate-manifest-on-startup>false</generate-manifest-on-startup>
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
37
<enableAppCache>false</enableAppCache>
<locale>
<default>en_US</default>
<availableLocales>
<localename>en_US</localename>
<localename>ja_JP</localename>
<localename>zh_CN</localename>
</availableLocales>
</locale>
</awpplatform>
Configuring the session timeout
1. Edit the platform.xml file. Change the disconnectCheckInterval parameter to to the
appropriate timeout value. This value is specified in seconds. The default timeout value is 180
seconds (3 minutes).
<disconnectCheckInterval>180</disconnectCheckInterval>
2. The HWE server will need to be restarted for the changes to be reflected after updating the
session timeout information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
38
4.9
Administration Guide
Configuring the HWE License Server
To change the license server configuration, modify the adminSettings.xml file. The location of this
file for a typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\\11.1\binaries\framework\data
on Linux
: /opt/altair/hwe/11.1/binaries/framework/data
adminSettings.xml file
<?xml version="1.0" encoding="UTF-8"?>
<Settings>
<Category name="Root">
<Category name="General">
<Setting name="savesession" preference="true">
<value>true</value>
<class>com.altair.awpf.services.preferences.model.BooleanPreference</class>
<displayName>Save Session</displayName>
<isEnforced>false</isEnforced>
<private>false</private>
</Setting>
<Setting name="notificationpanelstate">
<value>hide</value>
<class>com.altair.awpf.services.preferences.model.Setting</class>
<isEnforced>false</isEnforced>
<private>true</private>
</Setting>
</Category>
<Category name="License Server">
<Setting name="Location" preference="true">
<value>6200@trlicsrv03</value>
<class>com.altair.awpf.services.preferences.model.StringPreference</class>
<displayName>Server Location</displayName>
<isEnforced>true</isEnforced>
<private>false</private>
</Setting>
</Category>
</Category>
</Settings>
Configuring the license server
1. Edit the adminSettings.xml file and change the <port:hostname> of the license server.
<Category name="License Server">
<Setting name="Location" preference="true">
<value>6200@trlicsrv03</value>
<class>com.altair.awpf.services.preferences.model.StringPreference</class>
<displayName>Server Location</displayName>
<isEnforced>true</isEnforced>
<private>false</private>
</Setting>
</Category>
</Category>
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
2. The HWE server will need to be restarted for the changes to be reflected after updating the
license server information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
39
40
Administration Guide
4.10 Configuring HWE Language/Localization
To change the HWE localization/language settings, edit the platform.xml file. Currently, HWE
supports:
English
Chinese
The location of the platform.xml file for a typical installation of HWE is:
on Windows : C:\Program Files\altair\hwe\11.1\config
on Linux
: /opt/altair/hwe/11.1/config
platform.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!-A sample configuration for AWPF platform This configuration is
supposed to have various settings whic hare common for various
application spresent in the system.
All other application can derive application settings from here as derived configuration
-->
<awpplatform version="17.6.2" buildnumber="101220100800">
<customer>
<name>Altair</name>
<description>Altair Engineering</description>
<logouri>../login/resources/images/vendor/HyperWorks_logo.png</logouri>
<custombranding>
<![CDATA[<div class="customer-branding">HTML HERE</div>]]>
</custombranding>
</customer>
<copyright>LABEL_COPYRIGHT</copyright>
<contexlisteners>
<listener-class>com.altair.awpf.services.notification.core.NotificationDispatcherTimerTa
</contexlisteners>
<notification>
<dispatcher-interval>1000</dispatcher-interval>
</notification>
<preference>
<!--<preserver>com.altair.awpf.services.preferences.core.DBPreserveAndRestore</preserver
<preserver>com.altair.awpf.services.preferences.core.FilePreserveAndRestore</preserver>
</preference>
<eventregistration>
<platformevnet>
<listener>com.altair.awpf.services.notification.core.NotificationManagerEventLis
<listener>com.altair.awpf.services.preferences.core.SettingManagerEventListener<
</platformevnet>
Copyright © 1992 - 2012 Altair Engineering Inc.
Advanced Configuration
41
<applicationevent>
</applicationevent>
</eventregistration>
<!-- tab close check time interval in seconds -->
<disconnectCheckInterval>3600</disconnectCheckInterval>
<generate-manifest-on-startup>false</generate-manifest-on-startup>
<enableAppCache>false</enableAppCache>
<locale>
<default>en_US</default>
<availableLocales>
<localename>en_US</localename>
<localename>ja_JP</localename>
<localename>zh_CN</localename>
</availableLocales>
</locale>
</awpplatform>
Configuring HWE localization/language:
1. Edit the platform.xml and change the <default></default> XML element to the proper
language option. For example, to switch from a default of English to Chinese you would change
this:
<locale>
<default>en_US</default>
<availableLocales>
<localename>en_US</localename>
<localename>ja_JP</localename>
<localename>zh_CN</localename>
</availableLocales>
</locale>
to:
<locale>
<default>zh_CN</default>
<availableLocales>
<localename>en_US</localename>
<localename>ja_JP</localename>
<localename>zh_CN</localename>
</availableLocales>
</locale>
2. The HWE server will need to be restarted for the changes to be reflected after updating the
localization/language information.
Restart the HWE server on Linux
Restart the HWE server on Windows
Copyright © 1992 - 2012 Altair Engineering Inc.
42
5
Administration Guide
Location of HWE Files
The installation directory, which will be referred to as <HWE_INSTALL_DIR>, for a typical installation of
HWE is:
on Windows : C:\Program Files\altair\hwe\11.1
on Linux
: /opt/altair/hwe/11.1
Tomcat Web Server Files
The Tomcat web server configuration files can be found at <HWE_INSTALL_DIR>/thirdparty/
apache/tomcat/conf.
Apache Log4j Properties File
The Apache Log4J properties file can be found at <HWE_INSTALL_DIR>/config/log4j.
properties.
HWE Platform Configuration File
The HWE platform configuration file can be found at <HWE_INSTALL_DIR>/config/platform.
xml. This file is where HWE session timeout and language settings can be configured.
Postgres Configuration File
The Postgres configuration file can be found at <HWE_INSTALL_DIR>/thirdparty/apache/
tomcat/conf/context.xml.
HWE License Server Configuration File
The HWE license server configuration file can be found at <HWE_INSTALL_DIR>/binaries/
framework/data/adminSettings.xml.
HWE Authentication Configuration Files
The HWE Authentication Configuration Files can be found at <HWE_INSTALL_DIR>/config/
AAServiceHome/config.
Copyright © 1992 - 2012 Altair Engineering Inc.
Location of HWE Files
43
Log Files
HWE Log Files
The HWE log files can be found at <HWE_INSTALL_DIR>/logs
Apache Tomcat Logs
The Apache Tomcat log files can be found at <HWE_INSTALL_DIR>/thirdparty/apache/
tomcat/logs/catalina.out
Postgres Server Log
The Postgres server log files can be found at <HWE_INSTALL_DIR>/thirdparty/postgres/
hwedata/postgres_server.log
Copyright © 1992 - 2012 Altair Engineering Inc.
44
6
Administration Guide
Database Field Lengths
Database field lengths:
account_name
Character
varying(500)
application
Character
varying(500)
architecture
Character
varying(500)
check_point
Character
varying(500)
error_path
Character
varying(500)
execution_host
Character
varying(500)
hold_types
Character
varying(500)
jobid
Character
varying(500)
job_name
Character
varying(500)
job_state
Character
varying(500)
join_path
Character
varying(500)
keep_files
Character
varying(500)
mailstatus
Character
varying(1)
mail_points
Character
varying(500)
output_path
Character
varying(500)
pbs_job_directory
Character
varying(500)
queuename
Character
varying(500)
re_runnable
Character
varying(500)
sandbox
Character
varying(500)
servername
Character
varying(500)
session_id
Character
varying(500)
user_name
Character
varying(500)
Copyright © 1992 - 2012 Altair Engineering Inc.
Index
Index
-PPostgres
-AAccess Management Service
Advanced Configuration 19
-R-
3
restarting HWE 12, 16
Results Visualization Service
-CCompute Manager 3
configuring authentication 20
configuring HWE logging 34
configuring Postgres 32
configuring session timeout 36
configuring the language/localization
configuring the license server 38
copyright 5
database field lengths
40
starting HWE 10, 14
stopping HWE 11, 15
supported browsers 7
supported platforms 7
system requirements for CM 6
system requirements for CM + RV
third party licenses
trademark 5
44
-E29
-GGoogle Chrome Frame plug-in
7
-HHWE status 18
HyperWorks Enterprise
3
-Iinstallation location of HWE
17
-Llocation of HWE files
42
Copyright © 1992 - 2012 Altair Engineering Inc.
3
-S-
-T-
-D-
enabling SSL
32
5
6
45