HyperWorks Enterprise 11 - Altairresources.altair.com/pbs/documentation/support/HyperWorks... · HyperWorks Enterprise Administration Guide 11.1, Updated: 8/31/2012. ... Introduction

Administration Guide

HyperWorks Enterprise 11.1

Administration Guide2

Copyright © 1992 - 2012 Altair Engineering Inc.

Table of Contents

3Introduction to Hyperworks Enterprise1

................................................................................................................................... 5Copyrights, Trademarks, and Third Party Licenses

................................................................................................................................... 6System Requirements

................................................................................................................................... 7Supported Platforms

9HWE Portal Service on Windows2

................................................................................................................................... 10Starting HWE

................................................................................................................................... 11Stopping HWE

................................................................................................................................... 12Restarting HWE

13HWE Portal Service On Linux3

................................................................................................................................... 14Starting HWE

................................................................................................................................... 15Stopping HWE

................................................................................................................................... 16Restarting HWE

................................................................................................................................... 17Determining Installation Location of HWE

................................................................................................................................... 18Determining if HWE is Installed & Running

19Advanced Configuration4

................................................................................................................................... 20Configuring Access Management Service

................................................................................................................................... 25Configuring Administrative Users

................................................................................................................................... 26Configuring File Operations Performance

................................................................................................................................... 28Configuring JVM Performance

................................................................................................................................... 29Enabling SSL for HWE on Linux

................................................................................................................................... 32Configuring the Postgres Database

................................................................................................................................... 34Configuring HWE logging

................................................................................................................................... 36Configuring Session Timeout

................................................................................................................................... 38Configuring the HWE License Server

................................................................................................................................... 40Configuring HWE Language/Localization

42Location of HWE Files5

44Database Field Lengths6

Introduction to Hyperworks Enterprise 3


1 Introduction to Hyperworks Enterprise

HyperWorks Enterprise (HWE) is a modern Service Oriented Architecture coupled with the marketleading HPC workload management and job scheduling solution - PBS Professional® , constituting thefoundation of Altair's HPC offering. HyperWorks Enterprise increases high-performance computingproductivity, 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 managethe contents used throughout the simulation life cycle, working in an extremely intuitive and user-friendly Web-based interface.

Data Freshness

With HyperWorks Enterprise Solutions, users can immediately begin managing their personaldata or collaborating in small teams, without the overhead typical of enterprise data managementand 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 managementexperience, employing software and hardware resources to streamline complex analysis with afew mouse clicks.

Components available through the installation of HyperWorks Enterprise (for more information aboutHyperWorks Enterprise see the HyperWorks Enterprise Administration Guide, which can bedownloaded 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 beinstalled.)

Access Management Service

Results Visualization Service

Compute Manager

Compute Manage is a job submission and monitoring portal which enables users to run, monitor andmanage workloads on distributed resources remotely. Compute Manager uses the High PerformanceComputing workload management capability of Altair’s PBS Application Services and PBS Professionalfor efficient resource utilization, access to the cloud for job submission and subsequent accounting.




Results Visualization provides necessary features and functionalities to access, process and visualizeCAE results information through an easy and intuitive graphical user interface, embedded directly intothe web browser. This allows users to access these features anytime and from anywhere without theneed for installing any post processing applications on their desktop. In the current release, thesefeatures 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 accesscontrol policies. For more information about Access Management Service, you may download theAccess Management Service Administrator's Toolkit Command Reference Guide from the HyperWorksor PBSWorks documentation user area.

Compute Manager and Results Visualization Service must be installed separately. The ResultsVisualization Service must be installed to use the plug-in with Compute Manager. For more informationabout Compute Manager see the Compute Manager Installation and Administration Guide. For moreinformation about Results Visualization Service see the Results Visualization Service Installation andAdministration Guide. Both documents can be downloaded from the HyperWorks or PBSWorksdocumentation user area.



1.1 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®, PBSProfessional®, 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.



1.2 System Requirements

Minimum Hardware Requirements for Compute Manager

Hardware MinimumRequirement

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 MinimumRequirement

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 Services11.0.1 or later. Please contact your site administrator for further information.



1.3 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 filesnor the file upload progress meter in Compute Manager. It has been observed that many timesinstalling the Chromium projects Google Chrome Frame plug-in on Windows XP, Vista and Windows 7has provided indirect support for this. However, this configuration has not formally been tested, so it isnot fully supported by Altair. Please use the Chromium projects at your own discretion.


It is observed that installing Google Chrome Frame on IE 8 and 9 significantly improves theperformance of Results Visualization, especially plotting use cases. However, the plug-in appears to



have some random issues with the Hyperview Player plug-in, which sometimes leads to unexpectedbehavior during animation data viewing. In these instances, the generated animation file (h3d) can bedownloaded 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. Ifissues arise, it may be recommended to uninstall the plug-in.

To install and configure Google Chrome Frame see the Compute Manager Installation andAdministration Guide, which can be downloaded from the HyperWorks or PBSWorks documentationuser area.

HWE Portal Service on Windows 9


2 HWE Portal Service on Windows



2.1 Starting HWE

To start HWE:

1. Open Control Panel->Administrative Tools->Services

2. Right click on "HWE Portal Service" and click the "Start" option.

HWE Portal Service on Windows 11


2.2 Stopping HWE

To stop HWE:


2. Right click on "HWE Portal Service" and click the "Stop" option.



2.3 Restarting HWE

To restart HWE:


2. Right click on "HWE Portal Service" and click the "Restart" option.

HWE Portal Service On Linux 13


3 HWE Portal Service On Linux



3.1 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 serversudo -u user1 /opt/altair/hwe/11.1/scripts/startpostgres.sh /opt/altair/hwe/11.1/thirdparty/postgreswaiting for server to start.....LOG: database system was shut down at2012-08-11 09:39:35 EDTLOG: database system is ready to accept connectionsLOG: autovacuum launcher started doneserver startedPostgres server started, pid: 19832 [OK]Starting HWE Portal ServerPlatform : x86_6464 Bit machineUsing CATALINA_BASE: /opt/altair/hwe/11.1/thirdparty/apache/tomcatUsing CATALINA_HOME: /opt/altair/hwe/11.1/thirdparty/apache/tomcatUsing CATALINA_TMPDIR: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/tempUsing JRE_HOME: /opt/altair/hwe/11.1/thirdparty/javaUsing CLASSPATH: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/bin/bootstrap.jarHWE Portal Server started, pid: 19875You can access the portal using link http://hwesuse113-01.prog.altair.com:8086/hwe [OK]



3.2 Stopping HWE

To stop HWE:


/etc/init.d/hweportal stop

The following message will be displayed:

Stopping HWE Portal Server PID 17295: [OK]Stopping Postgres server PID 17249 [OK]



3.3 Restarting HWE

To restart HWE:


/etc/init.d/hweportal restart

The following messages will be displayed:

Restarting HWE Portal ServerStopping HWE Portal Server PID 19875: LOG: unexpected EOF on clientconnection [OK]LOG: received smart shutdown requestLOG: autovacuum launcher shutting downLOG: shutting downLOG: database system is shut downStopping Postgres server PID 19832 [OK]Starting Postgres serversudo -u user1 /opt/altair/hwe/11.1/scripts/startpostgres.sh /opt/altair/hwe/11.1/thirdparty/postgreswaiting for server to start....LOG: database system was shut down at2012-08-11 09:40:51 EDTLOG: database system is ready to accept connectionsLOG: autovacuum launcher started doneserver startedPostgres server started, pid: 20104 [OK]Starting HWE Portal ServerPlatform : x86_6464 Bit machineUsing CATALINA_BASE: /opt/altair/hwe/11.1/thirdparty/apache/tomcatUsing CATALINA_HOME: /opt/altair/hwe/11.1/thirdparty/apache/tomcatUsing CATALINA_TMPDIR: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/tempUsing JRE_HOME: /opt/altair/hwe/11.1/thirdparty/javaUsing CLASSPATH: /opt/altair/hwe/11.1/thirdparty/apache/tomcat/bin/bootstrap.jarHWE Portal Server started, pid: 20147You can access the portal using link http://hwesuse113-01.prog.altair.com:8086/hwe [OK]



3.4 Determining Installation Location of HWE

To determine the installation location of HWE:


cat /etc/hweportal.conf

The installation location is identified by SERVER_HOME:

SERVER_HOME=/opt/altair/hwe/11.1



3.5 Determining if HWE is Installed & Running

To check that HWE is running:


/etc/init.d/hweportal status

If HWE is running the following message will be displayed:

HWE Portal Server (pid 20147) is runningYou 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 Linuxcommand line prompt:

ps -ef | grep hwe

Advanced Configuration 19


4 Advanced Configuration



4.1 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 atypical 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 authenticationmethods should be used with caution.

Sample configuration files for all authentication methods are stored in the sample config filesdirectory. 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/env/jdbc/awpf";};

Super_User_Login { com.altair.jaas.module.DatastoreLoginModule Required; com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/env/jdbc/awpf";};



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/env/jdbc/awpf";};


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/env/jdbc/awpf";};


AA_jaas.config.win file

LoginModule { com.altair.jaas.module.ProcessRunnerWindowsLoginModule Required; com.altair.computemanager.security.jaas.ComputeManagerLoginModule Requisite datasource="java:comp/env/jdbc/awpf";};




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


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


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


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


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.





Changing the SSH server

1. Edit the AA_jaas.config file to change the SSH server that will be used to authenticate HWEusers. 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/env/jdbc/awpf";};


2. The HWE server will need to be restarted for the changes to be reflected after updating the SSHserver.



Changing the Datastore

1. Edit the Datastore.properties file to configure the datastore. The location of the file for atypical 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 propertyvalues.

java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactorycom.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$



2. The HWE server will need to be restarted for the changes to be reflected after updating the Datastoreinformation.



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. Forexample:

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/env/jdbc/awpf";};


2. The HWE server will need to be restarted for the changes to be reflected after updating the NISserver.





4.2 Configuring Administrative Users

During the installation of HWE, the installation process prompts for a userid and password that will beused 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 thisgroup using Access Management Service (AMS). As of the HWE 11.1 release, an AMS tool kit isavailable to manage users and groups. For more information about AMS see the Access ManagementService Administrator's Toolkit Command Reference Guide, which can be downloaded from theHyperWorks or PBSWorks documentation user area.



4.3 Configuring File Operations Performance

When a job is running and a user wants to view or download a file from the execution directory of thejob, HWE asks PBS Application Services (PAS) for the contents of the file in chunks. By default, HWEasks 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 parametersHWE_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



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 10users are simultaneously downloading the file, potentially 32*10 MB of RAM could be required just fordownloads. This can result in an OutOfMemory exception, therefore take careful consideration whendetermining the optimal value for this argument.

The HWE server will need to be restarted for the changes to be reflected after updating the JVMargument -DAIF_FILECHUNK_SIZE_MB:





4.4 Configuring JVM Performance

To sustain a large number of concurrent users (over 30), the Java Virtual Machine (JVM) heap sizemay need to be adjusted. Currently, the default JVM heap size is 1024 MB. If OutOfMemory errors orwarnings are reported in the CM log files, this value should be increased. It can be increased inmultiples of 256 MB.

Thie Java heap size default is stored in a script file called server-start.sh on Linux andhweportal.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.config"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 JVMargument -Xmx1024m





4.5 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 fora 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 theLinux 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 tomcat -keyalg RSA keysize 2048

After executing this command, you will first be prompted for the keystore password. The defaultpassword used by Tomcat is "changeit" (all lower case), although you can specify a custompassword if you like. You will also need to specify the custom password in the server.xmlconfiguration file, as described in step 3.

Next, you will be prompted for general information about this Certificate, such as company, contactname, and so on. This information will be displayed to users who attempt to access a secure page inyour 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 thisCertificate (as opposed to any other Certificates stored in the same keystore file). You MUST usethe same password here as was used for the keystore password itself. This is a restriction of theTomcat implementation. (Currently, the keytool prompt will tell you that pressing the ENTER key doesthis 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.



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 privilegedports (443), therefore a non-privileged port (8443) is used.



6. The HWE server will need to be restarted for the changes to be reflected:



7. Accept the Certificate:

From a web browser, navigate to https://<hostname>:8443 and accept the certificate whenyou are prompted by the browser.



4.6 Configuring the Postgres Database

HWE uses Postgres 8.3 which is bundled with the HWE installer. HWE can be changed to point to adifferent Postgres database by updating the context.xml file. The location of the file for a typicalinstallation 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"?><Context>

 <WatchedResource>WEB-INF/web.xml</WatchedResource> <Loader className='com.altair.awpf.classloader.AWPFWebappLoader' />

<Manager pathname="" />

  <Resource auth="Container" driverClassName="org.postgresql.Driver" maxActive="20" maxIdle="10" maxWait="-1" name="jdbc/awpf" password="user1" type="javax.sql.DataSource" url="jdbc:postgresql://localhost:6767/hwewebportal" username="user1"/></Context>



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" name="jdbc/awpf" password="user1" type="javax.sql.DataSource" url="jdbc:postgresql://localhost:6767/hwewebportal" username="user1"/>

1. To configure HWE to point to a different Postgres database, edit the context.xml file andchange the resource definitions for the datastore where:

POSTGRES_SERVER_HOST is the hostname or IP address of the host where Postgres isinstalled.

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 connectto the database.

POSTHRES_DB_PASSWORD is the Password for the Postgres user name.

<Resource auth="Container" driverClassName="org.postgresql.Driver" maxActive="20" maxIdle="10" maxWait="-1" name="jdbc/awpf" 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 thelogging information.





4.7 Configuring HWE logging

The HWE logging behavior can be defined in the file log4j.properties. The location of the filefor a typical installation of HWE is:

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.RollingFileAppenderlog4j.appender.frameworkRollingFile.File=awpflog.loglog4j.appender.frameworkRollingFile.MaxFileSize=2MBlog4j.appender.frameworkRollingFile.MaxBackupIndex=2log4j.appender.frameworkRollingFile.layout=org.apache.log4j.PatternLayoutlog4j.appender.frameworkRollingFile.layout.ConversionPattern= %n%p, %d{dd MMM yyy HH:mm:ss,SSS} -{%F: %L} - %m %nlog4j.rootLogger=INFO, frameworkRollingFile

Configuring logging behavior

1. You can define the level of logging by editing the log4j.properties file and setting theparameter 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 coarse-grained 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






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=2MBlog4j.appender.frameworkRollingFile.MaxBackupIndex=2






4.8 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:



platform.xml file

<?xml version="1.0" encoding="UTF-8"?> 

<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</listener-class> </contexlisteners>

<notification> <dispatcher-interval>1000</dispatcher-interval> </notification>

<preference>  <preserver>com.altair.awpf.services.preferences.core.FilePreserveAndRestore</preserver> </preference>

<eventregistration> <platformevnet> <listener>com.altair.awpf.services.notification.core.NotificationManagerEventListener</listener> <listener>com.altair.awpf.services.preferences.core.SettingManagerEventListener</listener> </platformevnet>

<applicationevent> </applicationevent> </eventregistration>

 <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 the session timeout

1. Edit the platform.xml file. Change the disconnectCheckInterval parameter to to theappropriate timeout value. This value is specified in seconds. The default timeout value is 180seconds (3 minutes).

<disconnectCheckInterval>180</disconnectCheckInterval>

2. The HWE server will need to be restarted for the changes to be reflected after updating thesession timeout information.





4.9 Configuring the HWE License Server

To change the license server configuration, modify the adminSettings.xml file. The location of thisfile 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>



2. The HWE server will need to be restarted for the changes to be reflected after updating thelicense server information.





4.10 Configuring HWE Language/Localization

To change the HWE localization/language settings, edit the platform.xml file. Currently, HWEsupports:

English

Chinese

The location of the platform.xml file for a typical installation of HWE is:



platform.xml file

<?xml version="1.0" encoding="UTF-8"?> 

<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</listener-class> </contexlisteners>

<notification> <dispatcher-interval>1000</dispatcher-interval> </notification>

<preference>  <preserver>com.altair.awpf.services.preferences.core.FilePreserveAndRestore</preserver> </preference>

<eventregistration> <platformevnet> <listener>com.altair.awpf.services.notification.core.NotificationManagerEventListener</listener> <listener>com.altair.awpf.services.preferences.core.SettingManagerEventListener</listener> </platformevnet>



<applicationevent> </applicationevent> </eventregistration>

 <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 properlanguage option. For example, to switch from a default of English to Chinese you would changethis:

<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 thelocalization/language information.





5 Location of HWE Files

The installation directory, which will be referred to as <HWE_INSTALL_DIR>, for a typical installation ofHWE 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.

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



6 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)

Index 45


Index- A -Access Management Service 3


- C -Compute Manager 3

configuring authentication 20

configuring HWE logging 34

configuring Postgres 32

configuring session timeout 36

configuring the language/localization 40

configuring the license server 38

copyright 5

- D -database field lengths 44

- E -enabling SSL 29

- G -Google Chrome Frame plug-in 7

- H -HWE status 18

HyperWorks Enterprise 3

- I -installation location of HWE 17

- L -location of HWE files 42

- P -Postgres 32

- R -restarting HWE 12, 16

Results Visualization Service 3

- S -starting HWE 10, 14

stopping HWE 11, 15

supported browsers 7

supported platforms 7

system requirements for CM 6

system requirements for CM + RV 6

- T -third party licenses 5

trademark 5

Documents

HyperWorks Enterprise 11 - Altairresources.altair.com/pbs/documentation/support/HyperWorks... · HyperWorks Enterprise Administration Guide 11.1, Updated: 8/31/2012. ... Introduction