MSC Enterprise Mvision

MSC Enterprise Mvision
Installation and System Administration Guide

Corporate
MSC.Software Corporation
2 MacArthur Place
Santa Ana, CA 92707 USA
Telephone: (800) 345-2078
Fax: (714) 784-4056
Europe
MSC.Software GmbH
Am Moosfeld 13
81829 Munich, Germany
Telephone: (49) (89) 43 19 87 0
Fax: (49) (89) 43 61 71 6
Asia Pacific
MSC.Software Japan Ltd.
Entsuji-Gadelius Building
2-39, Akasaka 5-chome
Minato-ku, Tokyo 107-0052, Japan
Telephone: (81) (3) 3505 0266
Fax: (81) (3) 3505 0914
Worldwide Web
www.mscsoftware.com
Disclaimer
MSC.Software Corporation reserves the right to make changes in specifications and other information
contained in this document without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes
only, and are not intended to be exhaustive or to apply to any particular engineering problem or design.
MSC.Software Corporation assumes no liability or responsibility to any person or company for direct or
indirect damages resulting from the use of any information contained herein.
User Documentation: Copyright  2008 MSC.Software Corporation.. Printed in U.S.A. All Rights
Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any
reproduction or distribution of this document, in whole or in part, without the prior written consent of
MSC.Software Corporation is prohibited.
The MSC.Software logo, MSC, Enterprise Mvision, Mvision and Patran are registered trademarks of
trademarks of the MSC.Software Corporation or its subsidiaries in the United States and/or other
countries.
NASTRAN is a registered trademark of the National Aeronautics and Space Administration. MSC
Nastran is an enhanced proprietary version developed and maintained by MSC.Software Corporation.
All other product names, brand names, or trademarks belong to their respective owners.
Publication Date: October 31, 2008

MVEN*V2008R1*Z*Z*Z*DC-OPS
C O N T E N T S
MSC Enterprise Mvision Installation and System Administration Guide
About This Guide ■ Introduction, 8

■ Organization of This Guide, 8
1
Introducing MSC ■ MSC Mvision Materials Information System Products, 10
Enterprise Mvision
■ Deliverables, 13
■ Related Documentation, 13
2
Installation ■ Overview, 16
Preparation and
■ Before Beginning the Installation, 16
Overview
■ Preparing for Installation on Windows XP, 17
■ Preparing for UNIX/Linux Installation, 19
■ General Memory Requirements, 24
■ Updating an MSC Enterprise Mvision Installation, 27
3
Installing MSC ■ Overview, 30
Enterprise Mvision
■ Requirements Before Installing MSC Enterprise Mvision, 31
■ Installing MSC Enterprise Mvision on Windows XP, 39
■ Installing MSC Enterprise Mvision on UNIX/Linux, 42
■ Configuring the Report Generator, 58
■ Installing MSC Enterprise Mvision Databanks, 60
■ Updating a Previous Release of MSC Enterprise Mvision, 61
4
Server ■ Overview, 64
Configurations,
■ MSC Enterprise Mvision Server Configurations and Configuration
Utilities, and Control Files, 65
Component
Information ■ Features and Utilities, 77
■ Log Files, 81
■ Installing the LDAP Database, 83
■ X Virtual Frame Buffer, 86
■ Migrating From Previous Versions, 90
■ SSL Encryption of the Integrated Client, 103
■ Security Query, 104
5
Configuration and ■ Overview, 106
User Access Files ■ Using MSC Enterprise Mvision Databanks, 107
■ General Administration Functions, 124
■ Legend Display Customization, 132
■ Configuration Files, 133
■ Customizing User Login Environment, 148
■ URL Utilities, 158
■ Implementing Export Functions for MSC Enterprise Mvision, 160
6
Administrative ■ Overview, 180
Panel Interface ■ Starting the Administrative Panel Interface, 181
■ Administrative Commands, 183
A
Installing FLEXlm
■ Overview, 188
■ Installing FLEXlm for a New UNIX/Linux Server, 189
■ Installing FLEXlm on a New Windows XP Server, 192
■ Replacing Codes on an Existing UNIX/Linux Server, 193
■ Replacing Codes on an Existing Windows XP Server, 194
■ Installing FLEXlm Using a Nodelock File, 194
■ MSC_LICENSE_FILE vs LM_LICENSE_FILE, 195
■ Additional Documentation, 195
B
Using the Batch ■ Getting Started with Batch Builder, 198
Builder ■ Batch Builder Program, 199
■ Running Batch Builder, 200
■ Batch Builder Menus, 201
■ Batch Builder Examples, 209
C
Troubleshooting ■ Overview, 216
MSC Enterprise ■ Emv Monitor Fails to Start (Windows XP), 216
Mvision
■ Emv Server Starting Repeatedly from the EmvMonitor, 216
■ A Server Fails to Start, 216
■ Large Property Curve/Figure Image Fails to display, 217
■ JSP pages for Administration Panel fails on Windows XP, 217
■ Microsoft Windows Service Fails to Stop Service, 218
■ Downloading Data to Excel Fails to Display the Excel, 219
■ Downloading files to Internet Explorer fails when SSL is enabled, 220
■ Downloading of Emv_Plot_Macro.xla Fails to Download Correctly to
Excel, 221
■ Troubleshooting the Formatted Report Generator, 221
7
About This Guide

■ Introduction
■ Organization of This Guide
8
Introduction
This guide contains all the information you will need to install and maintain MSC
Enterprise Mvision software. System-specific information is included so that you may
take full advantage of MSC Enterprise Mvision capabilities and features on your
system.
Organization of This Guide

This guide consists of the following chapters and appendices:
Introducing MSC Enterprise Mvision (Chapter 1) includes information about MSC
Mvision Materials Information System products. It also includes a list of MSC
Enterprise Mvision software, related documents, and deliverables.
Installation Preparation and Overview (Chapter 2) outlines the requirements and
procedures for installing and operating the MSC Enterprise Mvision software on the
Windows XP, Linux, and UNIX systems.
Installing MSC Enterprise Mvision (Chapter 3) contains complete step-by-step
instructions for installing MSC Enterprise Mvision software on the Windows XP,
Linux, and UNIX systems. This chapter also includes instructions for updating a
previous release.
Server Configurations, Utilities, and Component Information (Chapter 4) contains
detailed information on the server configuration settings, server software
requirements and server configuration files for operation of the MSC Enterprise
Mvision system.
Configuration and User Access Files (Chapter 5) contains detailed information on
using databanks, URL utilities, customizing the interface and implementing Export
functions.
Administrative Panel Interface (Chapter 6) includes information about the
Administrative Panel Interface, which allows you to update (invoke changes to user
access or system configuration files) for the MSC Enterprise Mvision system while
online.
Installing FLEXlm (Appendix A) summarizes FLEXlm installation procedures and
specifying license codes on servers for use with MSC Enterprise Mvision.
Troubleshooting MSC Enterprise Mvision (Appendix C) describes steps to resolve
common problems encountered with the installation or operation of MSC Enterprise
Mvision.
Using the Batch Builder (Appendix B) This chapter includes information on getting
started and running the program, menus, and examples.
1 Introducing MSC Enterprise Mvision
■ MSC Mvision Materials Information System Products

■ Deliverables
■ Related Documentation
10
MSC Mvision Materials Information System Products

The MSC Mvision Materials Information System currently includes the following
software and databank products:
MSC Mvision Software

• MSC Enterprise Mvision Builder - Easy-to-use software tool enabling users to
create a customized materials information system.
• MSC Enterprise Mvision Evaluator - Easy-to-use standalone software to
access and work with MSC-supplied or user-created materials databanks.
• MSC Enterprise Mvision - Direct access to MSC Mvision materials databanks
using standard web browsers.
• Patran Materials Enterprise - Direct access to MSC Mvision materials
databanks for the Patran analysis system.
• SimDesigner Materials - Direct access to MSC Mvision materials databanks
for the SimDesigner analysis system, available by special request.
• Patran Materials Enterprise - Direct access to MSC Mvision materials
databanks for the Patran analysis system.
MSC Mvision Databanks

• Standards Databanks:
MIL-HDBK-5/MMPDS Databank (Metals)
MIL-HDBK-17A Databank (Aerospace Composites)
MIL-HDBK-17F Databank (Polymer Matrix Composites)
PMC-90 Databank (Advanced Composites)
Metal Matrix Composites (MIL-HDBK-17-4)
ESDU Metallic Materials Data
• FEA Databanks
Analysis Databank
JAHM MPDB Temperature Dependent Properties
ASM High Temperatue Aluminum Properties
CHAPTER 1 11
Introducing MSC Enterprise Mvision
• Reference Databanks
Penton’s Materials Selector
PDL Chemical Compatibility of Plastics
PDL Effect of Temperature on Plastics
PDL Effect of Creep on Plastics
ASM Alloy Steel
ASM Aluminum
ASM Composites
ASM Copper
ASM Corrosion
ASM Magnesium
ASM Nylons
ASM Stainless Steels
ASM Structural Steels
ASM Thermoplastics
ASM Thermoset Plastics
ASM Titanium Databank
• ASM Cross Reference Databanks
ASM Woldman’s Engineering Alloys
ASM Worldwide Guide to Equivalent Irons & Steels
ASM Worldwide Guide to Nonferrous Metals & Alloys
• Producer’s Databanks
IDES Plastics Prospector
• Special Purpose Databank:
Fatigue
Fibers
Thermal
Electromagnetic Materials
Dytran
GE Plastics
• Demo Tutorial Databanks:
Demo_Composites
Demo_Metals
12
Overview of MSC Mvision Products
Programmatic
Analysis
Access
MSC Mvision
MSC Patran Materials
DPI™
Databanks
(Materials Libraries)
Design and
Programmatic
Customer-Defined
Databanks
Manufacturing
Access
MSC Mvision
Materials • Materials Test MSC Mvision Evaluator
DPI™
Programmatic
Authority
Access • Corp. Knowledge
MSC Mvision • Design
MSC Mvision Builder Allowables
DPI™
MSC-Supplied Programmatic
Programmatic
Databanks Access
Access
MSC
MSCMvision
Mvision DPI
• Producers DPI™
MSC Enterprise Inte-
• Standards grated Client
• Reference
• CrossReference
Programmatic
Worldwide Users
Access
MSC Enterprise
MSC Mvision Mvision
Patran Materials Enter-
DPI™
prise
Overview of MSC Mvision Product Line
For more information on the full line of MSC.Software

products, contact your MSC.Software Sales Representative.
CHAPTER 1 13
Introducing MSC Enterprise Mvision
Deliverables
The MSC Enterprise Mvision delivery package consists of the following items:
• MSC Enterprise Mvision CD-ROM
• MSC Enterprise Mvision Cover Letter
• MSC Enterprise Mvision User Interface Implementation Guide
• MSC Enterprise Mvision Installation and System Administration Guide
• MSC Enterprise Mvision Release Notes
• MSC Software Authorization Key Request Form
Related Documentation
These listed documents are useful for understanding the MSC Enterprise Mvision
system and software. The following documents are included with the MSC Enterprise
Mvision software:
• MSC Enterprise Mvision Release Notes
• MSC Enterprise Mvision User Interface Implementation Guide
• MSC Enterprise Mvision Integrated Client Installation and Implementation Guide
The following documents could also be useful and can be obtained from your
MSC.Software representative.
• MSC Mvision Building Databanks
• MSC Mvision Builder and Evaluator User's Guide
• MSC Mvision Database Programmatic Interface Manual
14
2 Installation Preparation and Overview
■ Overview
■ Before Beginning the Installation
■ Preparing for Installation on Windows XP
■ Preparing for UNIX/Linux Installation
■ General Memory Requirements
■ Updating an MSC Enterprise Mvision Installation
16
Overview
This chapter specifies the software and hardware requirements for installing and
operating the MSC Enterprise Mvision software on your computer system. It also
outlines procedures required to prepare your computer system for installation of the
MSC Enterprise Mvision software. We recommend that you read this chapter before
installing MSC Enterprise Mvision. The next chapter, Installing MSC Enterprise
Mvision, provides detailed installation instructions for the MSC Enterprise Mvision
software on all supported platforms.
Before Beginning the Installation

Before you begin installation of MSC Enterprise Mvision, please note the following:
• Your installation package comes with a CD-ROM containing all required
files.
• Perform all installation procedures when no one is using MSC Enterprise
Mvision to avoid unpredictable results.
• The entire installation procedure should take less than one hour.
• Before you begin, review the system requirements for your computer
system.
• Before you can finish the installation, you will need to obtain the FLEXlm
license codes to run MSC Enterprise Mvision. Ask your local MSC.Software
sales representative for assistance on this important step of the installation.
The MSC Enterprise Mvision system has certain software and hardware prerequisites.
You must verify that your system meets these minimum requirements. There are also
additional configuration options that will improve the performance of MSC
Enterprise Mvision on your system. We recommend that you make these
modifications for optimum performance.
Please read the following sections before attempting to install the MSC Enterprise
Mvision software.
CHAPTER 2 17
Installation Preparation and Overview
Preparing for Installation on Windows XP

Hardware Requirements
MSC Enterprise Mvision 2008r1 is available for installation on PCs running Microsoft
Windows XP.
A full installation of the MSC Enterprise Mvision system with nominal performance
requires a minimum of 128 M of RAM and a clock speed of 400 MHz. These are
minimum requirements for RAM and clock speed. Increasing either should improve
the system response to web requests and the allowable number of simultaneous users.
The XY-Graphics component of MSC Enterprise Mvision generates PNG (Ping)
images of the data to be plotted. This image-generation server, the
FigureToPngImageServer, requires either JRE or JDK to be installed. Follow the
installation instructions specified in the Required Software on the Server on page 18.
Hardware Server
• Windows XP compatible PC
• Pentium II 400 processor (minimum)
• CD-ROM drive
• Disk space requirements for MSC Enterprise Mvision 2008r1 are:
• 44 Mb (for core application)
• 1 gbyte (for MiKTeX software, if installation of the formatted report
generator is desired.)
• + total size of installed databanks
• + total size of auxiliary databank files (index files are not needed)
• Virtual memory requirements for MSC Enterprise Mvision 2008r1 are:
• 6 Mb (for core application)
• + sum of (1.5 to 3 times size of each databank, depending on its
structure)
• + 100 Kb per databank (for configuration files)
• + size of largest single databank reference file (for example, pdf, text,
or image file)
• + 5 to 10 Mb per concurrent user
18
Software Requirements
To fully enable the features and functionality of MSC Enterprise Mvision, the following
software must be installed on the Server: a Java Servlet-enabled Web server, a Java Server, a
LaTeX package to support the new PDF formatted report generator, and Adobe Acrobat to
enable viewing of documents stored in the <emv_install>/docs directory.
For viewing or processing purposes, other software or applications may be required on the
server and/or client. This is dependent on the specific requirements of your site or databank
contents.
Microsoft Visual C++ 6.0 is required to customize external functions using provided
workspace and project files.
Required Software on the Server

• Operating system - Windows XP
• MSC Enterprise Mvision requires installation of a Java Servlet-enabled Web
server. Suitable options include:
• Sun Java(TM) System Web Server 6 or higher software, which you can
download from:
http://www.sun.com/download/index.jsp?cat=Web%20%26%20Proxy%
20Servers&tab=3&subcat=Web%20Servers
It is recommended that you install all current service packs or patches

to this software. Installation instructions and requirements are
available this Web site:
http://docs.sun.com/db/doc/817-6095-10/
• BEA WebLogic Server 6.1 or higher

• IBM WebSphere Advanced Server 4.1 or higher
• Jakarta Tomcat 5.x or higher, available from:
http://tomcat.apache.org/download-55.cgi
• . The system requirements for running the Sun Server include:

• JDK release: 1.4.1_03 minimum
• Memory: 128 MB minimum, 512 MB recommended; 512 MB
minimum for Windows
• Disk Space: 150 MB (minimum) for the Solaris Operating System and
100 MB (minimum) for Windows; 200 MB recommended for both
Solaris and Windows platforms.
• We also recommend that you obtain and install a HTML/JavaScript editor
for customizing the MSC Enterprise Mvision HTML templates.
CHAPTER 2 19
• The Acrobat Reader software used for viewing MSC Enterprise Mvision
documentation on your server is provided on the CD-ROM. Select this item
during the installation process.
• New in EMV2008r1 is a formatted report generator, which requires
installation of MiKTeX 2.5. This OpenSource software package is available
at:
http:www.miktex.org
Required Software on the Client

• Any hardware (PC, Mac, UNIX) running Netscape 4.06 and above or Internet
Explorer 4 and above.
• Microsoft Excel 97 (used for local processing and display of Excel data files)
or any other spreadsheet program that can read tab delimited data files.
• Other software or applications may be required depending on your specific
site requirements and/or the contents of specific databanks.
Preparing for UNIX/Linux Installation

Hardware Requirements
MSC.Software has utilized the latest hardware and software for development and
quality assurance testing. This release supports the following operating systems for all
components of the MSC Enterprise Mvision 2008r1 system including the server,
Integrated Client, Security AP and UserSecurity dynamically loaded libraries:.
Operating
Manufacturer Version Compiler
System
Sun Solaris 8, 9, 10 5.2, 5.3
HP HP-UX 11.x, 11i 3.13
IBM AIX 5.1, 5.2 3.6.6
Intel x86 Window XP Visual Studio 6
Intel x86 RedHat RedHat Enterprise gcc 3.2.53
Linux AS 3.0, 4.0
Intel x86 SuSe Enterprise 9 gcc 3.3
UNIX workstations have no special requirements. Refer to Required Hardware and

Software Configurations, on page -21.
20
Software Requirements
To fully enable the features and functionality of MSC Enterprise Mvision, the following
software must be installed on the Server: a Java Servlet-enabled Web server, a Java Server, a
LaTeX package to support the new PDF formatted report generator, and Adobe Acrobat to
enable viewing of documents stored in the <emv_install>/docs directory.
For viewing or processing purposes, other software or applications may be required
on the server and/or client. This is dependent on the specific requirements of your site
or databanks contents.
Required Software on the Server

• Operating system - See the supported operation system in the table above.
• The current version of the software supports the following web servers:
• Sun Java System Web Server 6.1 or higher, which can be downloaded
from:
• BEA WebLogic 6.1 or higher. To obtain information on this server,
see:
http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/p
roducts/server
• Sun Java(TM) System Web Server 6 or higher software, which you can
download from:
It is recommended that you install all current service packs or patches

to this software. Installation instructions and requirements are
available this Web site:
http://docs.sun.com/db/doc/817-6095-10/
• BEA WebLogic Server 6.1 or higher
http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/p
roducts/server
• IBM WebSphere Advanced Server 4.1 or higher
• Jakarta Tomcat 5.x or higher, available from:
http://tomcat.apache.org/download-55.cgi
• We also recommend that you obtain and install a HTML/JavaScript editor

for customizing MSC Enterprise Mvision HTML templates.
CHAPTER 2 21
• The complete TeXLive installation and ps-tricks available from the TeXLive
website: http://ww.tug.org/texlive.
The latest image is located at:
http://www.ctan.org/tex-archive/systems/texlive/Images
The pstricks files are found at:

http://tug.ctan.org/tex-archive/graphics/pstrics/base/base.zip
www.ctan.org/texlive/graphics/pstrics/contrib/pstricks-add
• The Acrobat Reader software used for viewing MSC Enterprise Mvision
documentation on your server is provided on the CD-ROM. Select this item
during the installation process.
Required Software on the Client

• Any hardware (PC, Mac, UNIX) running Netscape Navigator 7.2 or Internet
Explorer 6.0.
• Microsoft Excel 97 (used for local processing and display of Excel data files)
any spreadsheet program or file reader that can handle tab-delimited data
files.
• Other software or applications may be required depending on your specific
site requirements and/or the contents of special databanks.
Memory Requirements for UNIX Workstations

MSC Enterprise Mvision performance is affected by the availability of care memory
and system swap space. As a minimum, you should have at least 128 megabytes of real
memory but MSC recommends 256 megabytes or more of real memory to minimize
swapping when running MSC Enterprise Mvision with large databanks or large
spreadsheets. Refer to General Memory Requirements on page 24 for more information.
Required Hardware and Software Configurations

The mscinfo Utility
MSC Enterprise Mvision provides the mscinfo utility for obtaining required system
information for MSC Enterprise Mvision installations.
The mscsetup utility executes this utility. Alternatively, you can run the mscinfo utility
from the MSC Enterprise Mvision installation using:
<installation_dir>/emv2008r1/bin/mscinfo
22
Note: You must have root access to obtain complete graphics and virtual memory
information on Hewlett Packard HP-UX. However, if you have normal
access, you can get to all other data.
mscinfo Utility Option Flags
mscinfo option: Use:

mscinfo -x Displays information pertaining to the Xserver. You must
run from a window being displayed on the machine in
question.
mscinfo -commands Displays a list of the commands used to determine system
information.
RAM, Swap, and Disk Space

MSC Enterprise Mvision hardware requirements vary according to databank size and
the functions being executed. Be aware that solvers or other software that run
concurrently with MSC Enterprise Mvision will also increase RAM, swap, and disk
space requirements.
Total memory is the sum of swap space and RAM. A given process requires a
minimum amount of total memory. If the minimum memory to execute a process is
more than the total memory available, MSC Enterprise Mvision generates memory or
memory allocation (malloc) errors. Some operating systems simply close with a
segmentation violation.
Because RAM is very fast in comparison to the disk-based swap, more RAM generally
translates into better performance. As a general rule, provide 25% to 30% of total
memory as RAM. Consult your operating system documentation for additional
information.
The following table lists disk space, swap, and RAM guidelines. MSC Enterprise
Mvision may actually run with fewer resources than shown, but we recommend these
minimums for practical use of MSC Enterprise Mvision.
Disk Space, Swap, and RAM Guidelines
Resource: Minimum: Standard:

RAM per user 128 Mb 256 Mb
Paging Disk Space 300 Mb 500 Mb
(Swap)
Scratch Disk Space 50 Mb 100 Mb
(/tmp)
CHAPTER 2 23
The mscsetup utility indicates required disk space for each product set.
Note: The installation process requires some small additional space for file
decompression. At most, decompression requires about 50 MB beyond
product disk requirements, but 10 MB of additional space is typical. If
sufficient space is not available in the installation directory, the mscsetup
utility attempts to use /tmp for decompression.
HP-UX Kernel Settings

The HP-UX operating system contains a utility named SAM that allows you to tune
many different kernel parameters. We recommend the following settings:
HP-UX Kernel Settings
Parameter: Description: Default: Recommended:

maxdsiz Maximum Data Segment Size 64Mb 90% of swap
maxtsiz Maximum Text Segment Size 64Mb 90% of swap
maxssiz Maximum Stack Segment Size 8Mb 67108864 (64 Mb)
MSC Enterprise Mvision needs more than 64Mb of virtual memory to run. If the
default maxdsiz is too low, this can cause MSC Enterprise Mvision to run out of virtual
memory unless both the swap and the maxdsiz parameters are increased.
MSC Enterprise Mvision does not exceed the 64Mb maxtsiz parameter, you are not
required to change this parameter.
Performance Tuning
To increase performance on the HP platform, we recommend the following settings:
Performance Settings
Parameters: Setting: Default:

fs_async 1 0
default_disk_ir 1 1 on HP700 class;
0 on HP800 Class
maxusers 100 32
fs_async and default_disk_ir set to 1 enables asynchronous disk writes and disk
write caching. This enables MSC Enterprise Mvision to perform I/O faster, because
the application will not wait to verify that the write was completed. The only problem
24
with the increased performance settings is that if the computer crashed at just the
wrong moment, the disk write may not have completed. However, since MSC
Enterprise Mvision probably crashed at the same time, it may be irrelevant that the
write did not complete. These parameters are actually for large network cluster
applications such as on-line transaction processing where data integrity is the primary
concern at all times.
Maxusers sets the maximum number of users, but more importantly, it lets SAM tune
other parameters that can increase the performance of MSC Enterprise Mvision.
Setting all three of these parameters to the above settings may have a significant effect
on the performance of MSC Enterprise Mvision, particularly I/O speed.
General Memory Requirements

The following general memory requirements apply to both Windows XP and
UNIX/Linux installations.
Memory Requirements for MSC Enterprise Mvision Core

Application
Disk Space Required:
Approximately 48 Mb for the Windows XP platform and 76 MB for UNIX/Linux
platforms, which includes all system files and auxiliary applications.
Virtual Memory Required:

Approximately 6 Mb, for the core application running with no users or databanks.
Memory Requirements for Databanks Used with MSC Enterprise

Mvision
Adequate disk space must be available for all databanks installed for use with MSC
Enterprise Mvision. All databanks and referenced files must be on or mapped to the
same drive.

In MSC Enterprise Mvision, databanks are always open (in virtual memory), and each
databank requires virtual memory of 1.5 to 3 times the size of the databank. Flat
databanks with a large number of scalar attributes require more space than databanks
containing mainly curves. The additional memory requirement (that is, more than the
size of the databank) is due to the creation of a virtual index to the databank to
enhance performance. This indexing is not performed when the databank is initially
loaded (at startup of server), but is performed when that databank is first accessed by
CHAPTER 2 25
a client. This means that the memory will not be immediately allocated but will be
required during subsequent operation. A databank similar to mil5.des, which is 7.6
Mb, will require approximately 11 Mb.
To use the entire library of MSC databanks would require approximately 700 Mb, plus
47 Mb for the auxiliary files. Because databank indexing is done in virtual memory by
MSC Enterprise Mvision, the physical index files as supplied with MSC Databanks are
not required, and can be deleted to save disk space if not used by other MSC Mvision
applications.
Memory Requirements for Auxiliary Databank Files Used with MSC

Enterprise Mvision
Adequate disk space must be available for all databank related files, including the
units (.unt) and mapping (.mapping) files, and any document or image files that can
be addressed by MSC Enterprise Mvision.
The units file is always open, but is typically a very small file. The mapping file is only
opened during the export process and requires temporary memory allocation. The
addition of forms to the Configuration file does increase the size of the Configuration
file, but this is usually insignificant. Typically these files will require less than 100 kb
per databank.
Other files such as documents and images are opened and closed as required during
operation. Enough memory should be allocated to open the largest document or
image which can be addressed for each databank. (For the MSC-supplied
mil5_new.des in theory this would be 43.5 Mb, due to the large PDF version of the
whole handbook. However, in practice, few companies implementing MSC
Enterprise Mvision would want users downloading 44 Mb files as part of a normal
browser session.)
Memory Requirements for User Sessions

No disk space is required for a user session. This is a temporary instance and is not
recorded or stored on disk.

The amount of virtual memory required for each user is primarily dependent on the
actions and the current state of the user's requests.
26
To sustain a user session with no requests requires approximately 50 Kb, but this
requirement is typically insignificant in comparison to the memory requirement to
service the user's actual request. If the user is displaying a detailed material list of a
databank, this will typically require 1 to 2 Mb of virtual memory. If the user is
displaying a 10,000 point curve (curve images are generated and transmitted by MSC
Enterprise Mvision as requested), this will typically require 2.5 to 5 Mb. If the
databank contains very large curves or images, this minimum requirement should be
increased accordingly.
Other operations, such as search functions and exporting data, also impose temporary
memory requirements. These memory requirements are cumulative in that each
additional simultaneous user requires the same amount of virtual memory. Therefore,
we recommend that at least 5 Mb to 10 Mb be provided for each simultaneous user to
provide acceptable performance.
CHAPTER 2 27
Updating an MSC Enterprise Mvision Installation

The installation script, mscsetup, is used by all MSC software and places all MSC
software in a common directory with individual products stored in subdirectories.
These subdirectories are labeled with the software name and version. Release 2008r1
of MSC Enterprise Mvision is placed in a subdirectory named emv2008r1. Auxiliary
software, such as Adobe FrameViewer and Adobe Acrobat, are placed in their own
subdirectories.
With this scheme, you can put several versions of MSC Enterprise Mvision in the same
directory and switch versions by referring to the subdirectory that contains the
version you want by its name. You can also load a new version of the software and test
it without affecting users who are using an older version.
28
3 Installing MSC Enterprise Mvision
■ Overview
■ Requirements Before Installing MSC Enterprise Mvision
■ Installing MSC Enterprise Mvision on Windows XP
■ Installing MSC Enterprise Mvision on UNIX/Linux
■ Configuring the Report Generator
■ Installing MSC Enterprise Mvision Databanks
■ Updating a Previous Release of MSC Enterprise Mvision

30
Overview
This chapter and the following chapter provide the detailed information required for
the installation and configuration of the MSC Enterprise Mvision software on
Windows and UNIX variant systems. We recommend that you read these chapters
thoroughly before starting the installation.
This chapter provides an outline of the overall installation and the steps necessary to
install and configure MSC Enterprise Mvision. These procedures include the
installation of all required third-party products.
The basic MSC Enterprise Mvision installation process involves these phases:
• Installing and configuring the Web Server
• Installing the FLEXlm license server
• Installing the MSC Enterprise Mvision software
Note: To perform these procedures you must have administrative privileges on the
Windows platform. You may also need root privileges on the UNIX/Linux
platforms on which MSC Enterprise Mvision is to be installed.
This chapter provides a thorough discussion of the installation of the basic (core
application) MSC Enterprise Mvision software. Refer to Appendix A of this guide for
more information on installing the FLEXlm software and refer to the MSC Enterprise
Mvision Integrated Client Installation and Implementation Guide for more information on
installing the Integrated Client software.
CHAPTER 3 31
Installing MSC Enterprise Mvision
Requirements Before Installing MSC Enterprise

Mvision
Installation of MSC Enterprise Mvision 2008r1 requires:
• One of the following Java Servlet-enabled Web servers: Sun ONE Enterprise
Server 6.0 or higher, BEA WebLogic Server 6.1 or higher, IBM WebSphere
Advanced Server 4.1 or higher, and Jakarta Tomcat 5.x or higher. Refer to the
vendor’s documentation for installation instructions.
• A current version of LaTeX (Unix) or MiKTeX (Windows).
MSC Enterprise Mvision 2008r1 is bundled with the Sun Java JRE 1.4.2_06 software,
which is installed automatically.
Web server applications like MSC Enterprise Mvision are I/O-intensive applications,
and the number of concurrent users your system can support may be limited by the
total number of available sockets allowed for your system. A node lock license file
may be required. If you anticipate a very large number of concurrent users, contact
your MSC.Software representative to determine if your system is configured correctly
for this application.
Additional third-party software may be required to support MSC Enterprise Mvision:
• Acrobat Reader (used for viewing user documentation on server)
• Optional - HTML/JavaScript editor for customizing HTML templates
• Optional - LDAP from Netscape or another vendor for URL/User/Group
Installing LaTeX
There are four reporting options available in MSC Enterprise Mvision 2008r1:
• The original HTML hardcopy
• XML - simple XML output of selected records, which can be formatted using
XSLT stylesheet technology.
• Formatted HTML, which includes custom formats, header, footer, curve
legends, and prints curve points.
• PDF Report Generator , which includes all the feature of the Formatted
HTML, but uses LaTeX technology to generate the PDF.
The LaTeX instalation files are available as OpenSource software from the following
URL’s:
Windows The Complete MiKTeX 2.5 http://miktex.org/

UNIX/Linux The Complete TeX Live http://www.tug.org/texlive/
32
Installing MiKTeX 2.5 on Windows

The following sections discuss the download and installation of MikTeX on Windows
XP platforms.
1. Download the “MikTeX Net Installer from: http://miktex.org .
2. Run the setup-xxx.exe file; read and accept the copying agreement.
3. Choose to ‘Download MiKTeX’.
4. Choose ‘Complete MiKTeX’ (about 400MB).
5. Select a mirror in you own country.

6. Choose where the packages should be installed or keep the default.
7. Wait for the MiKTeX installer to install all LaTeX packages.
To install MiKTeX, perform the following:
1. Run the setup-xxx.exe installer once again.
2. Accept the copying agreement.
3. Choose ‘Install MiKTeX.’
CHAPTER 3 33
4. Choose to install the ‘Complete MiKTeX.’
5. Choose ‘Install for Anyone.’

6. Choose the location of the packages or use the default.
Ensure that LaTeX binaries are in your path or add them to the file:
<emv_install_dir>/bin/GemeratePdfReport.bat
Installing TeXLive 2007 on UNIX/Linux

It is suggested that you study the Live manual before installing TeXLive. It is available
at: http://www.tug.org/texlive/doc/texlive-en/live.html.
The main page for TeXLive is
http://www.tug.org/texlive/ . The latest image is located at
http://www.ctan.org/tex-archive/systems/texlive/Images/.
1. Download the file “texlive-inst.iso.zip” (638MB).
34
2. Download the pstricks and pstricks-add packages or use the given

pstricks-update directory.
http://tug.ctan.org/tex-archive/graphics/pstricks/base/base.zip
http://www.ctan.org/tex-archive/graphics/pstricks/contrib/pstricks-add
To install TeXLive, burn the downloaded ISO image to a CD-R or mount it to the file
system.
1. Run the installation program: (assuming CD-R mounted in /dev/cdrom)
cd /mnt/cdrom/texlive/
sh install-tl.sh
2. Ensure that all packages are selected and modify the paths to suit your system
setup.
3. Add the latex binaries to your path, default installation directory is:
/usr/local/texlive/2007/bin/<arch>
Alternatively add the binary path to

<emv_install_dir>/bin/GeneratePdfReport.bat
Unzip the ptricks and pstricks-add files into a directory. The following instructions
assume a default TeXLive installation directory:
/usr/local/texlive/2007/texmf-dist
If you are using pstricks-update, simply merge the contents of the directory into
the installation directory of TeXLive.
After downloading, map the files and directories as follows:
From To (/usr/local/texlive/2007/texmf-dist)
pstricks/dvips/* dvips/pstricks/
pstricks/generic/* tex/generic/pstricks/
pstricks/latex/* tex/latex/pstricks/
pstricks-add/pstricks-add dvips/pstricks-add/pstricks-add.pro
.pro
pstricks-add/pstricks-add tex/generic/pstricks-add/pstricks-ad
.tex d.tex
pstricks-add/pstricks-add tex/latex/pstricks-add/pstricks-add.
.sty sty
After updating the files above, run texhash rebuild the file location tables.
CHAPTER 3 35
FLEXlm License System

The FLEXlm license system must be installed before running the MSC Enterprise Mvi-
sion server. See Appendix A (p. 187) for information on installing and configuring
FLEXlm.
To verify that the FLEXlm license system has been installed and configured properly:
• Verify that the system environment variable MSC_LICENSE_FILE is set to a

valid MSC FLEXlm license file or server.
If it is not, the MSC Enterprise Mvision server does not start.
To verify the license system output:
• Check the log file AdminLog.txt in the <emv_root>/log directory. This file
indicates if the license system is functioning properly.
Auto-Deployment of EMV
MSC Enterprise Mvision is automatically deployed on Windows to an installed Web
application server using InstallShield. On UNIX and Linux platforms, deployment is
invoked using the configure script.
Installation Directories
The installation root directory (after installing the MSC Enterprise Mvision software)
contains all of the MSC Enterprise Mvision configuration and runtime files.
Numerous subdirectories exist which contain information for different components of
the system.
The following lists the subdirectories and the file or information included in each
subdirectory:
Subdirectories
The subdirectory: Contains:

Xvfb X virtual frame buffer for headless devices (UNIX only).
bin Executable files, scripts, and system images
config Configuration files for users, databases, and properties
files, and so on
databases Default location for MSC Mvision databanks and
support files
doc Online documentation
external_functions Perl scripts, odl files, export templates and executables,
and so on
36
Subdirectories
The subdirectory: Contains:

html MSC Enterprise Mvision HTML template files
install Configuration scripts to be run after installation (UNIX
platforms)
IntegratedClient All files required to run the EMV Integrated Client
application
ior Interoperable reference directory dynamic content
(Windows systems)
jars MSC Enterprise Mvision required jar files
java Java developer kit and runtime environment (Windows
systems)
lib Shared libraries for UNIX platforms.
jre Java runtime environment (UNIX)
log MSC Enterprise Mvision system log information
perl Perl executables and supporting files
security MSC Enterprise Mvision authorization file, user
password file
resources Message catalogs (UNIX)
src Customizable MSC Enterprise Mvision shared libraries

(Security API)
uninstaller Uninstall application for MSC Enterprise Mvision and its
components (Windows systems)
web_server As-delivered Web-server configuration files and war
file(s)
The Administration files are a set of files used by MSC Enterprise Mvision. Within
these files, the data, such as users, security, group configurations, HTML template
files, and so on, are managed. Access to this information is through the MSC
Enterprise Mvision root directory.
The Administration files are in the directories that are specified in the properties file
for each server. The bin, config, databases, external_functions, html, and security directories
can be located anywhere on the file system. The remaining directories must be located
relative to the MSC Enterprise Mvision root directory.
CHAPTER 3 37
The following directories are specified in the properties file for each server:
Directories Specified in the Properties File
The directory: Contains:

bin Executable files, scripts, and system images.
config EmvMonitor.properties, Databases.txt, Emv.properties,
EmvApi.properties, EmvApiXml.dtd,
EmvHardcopy.properties, EmvReport.sty, Admin.properties,
FigureToPngServer.properties, Global.properties,
GroupConfiguration.txt, InitialUrl.txt, Messages.properties,
MimeTypeMappings.properties, UserList.txt,
WebServer.properties., MscIntegratedClient.properties,
MSCUnits.dtd, wsdeploy.py.
databases Installed databanks and support files.
external_ Perl scripts, schema.odl, MSC Mvision export templates, export
functions
executable, C++ and Perl customization directories.
html Any files referenced as MSC Enterprise Mvision HTML
template files. These include the simple and advanced interface
(mv3x) and mv3x_pw (Power User Advanced MV3X) HTML
files.
security SecDbUser.txt, SecUser.txt, SecQuery.txt
The following directories must be located relative to the MSC Enterprise Mvision
root directory:
jars OB.jar, EmvChart.jar, EmvChartAll.jar, EmvChartPng.jar,
EmvDbTrans.jar, EmvMonitor.jar, EmvWebServer.jar,
FormDefToGrp.jar, Idl.jar, jbcl3.1.jar, jcchart363j.jar,
jcchart450K.jar, AddDefDbNavView.jar, servlet.jar, sfc.jar,
swingall.jar, symbeans.jar
java Java subdirectory containing Java 1.4 files required to support
the charting tools.
log AdminLog.txt, EmvLog.txt, EmvMonitorLog.txt,
FigureToPngImageServerLog.txt, ProLogOutput.txt,
WebServerLog.txt
perl Perl subdirectory containing data used by the Perl shell
command.
38
Directories Specified in the Properties File (Continued)
The directory: Contains:

src • Security API - This is a user-customizable dll that
controls the user’s access to MSC Enterprise Mvision
using a user ID/password validation system. This API
can be customized for a specific set of rules for
validating the user ID/password and returning the
status to EMV.
• UserLoginDLL - This is a user-customizable dll that
supports customized access to the login security
functionality, such as pre-filtered logins, LDAP
configuration, WSSO, and others.
• MsgListener.java - A Java interface used to customize
the EmvMonitor and WebServer message logging.
• MsgLogException.java -
ior Interoperable reference directory dynamic content
tmp Stores temporary files used in the generation of the formatted
html and PDF hardcopy reports. This directory may be emptied
periodically.
CHAPTER 3 39
Installing MSC Enterprise Mvision on Windows XP

This section details the installation of the software on Windows XP computer systems.
It is recommended that you read this chapter thoroughly before starting the
installation.
Prerequisites:
• Check the system configuration requirements as outlined in Chapter 2 to
ensure your system is ready for a MSC Enterprise Mvision software
installation. If your system does not meet the minimum requirements
outlined in this chapter, you will have to correct the problems before you can
complete the installation.
• You must have administrator privileges to install MSC Enterprise Mvision.
• Verify that you have a supported Web server installed.
• Verify that the Web Server is configured.
• To verify that the FLEXlm license system is installed and configured, check
that the system environment variable MSC_LICENSE_FILE is set to a valid MSC
FLEXlm license file or server. If it is not, the MSC Enterprise Mvision server
will not start. Check the AdminLog.txt file in the <emv_root>/log directory
which will indicate if the license system is functioning properly.
IThe setup.exe installation application performs all the steps necessary to get the
MSC Enterprise Mvision and MSC Enterprise Mvision Integrated Client applications
up and running.
To run the setup.exe application:
1. Insert the MSC Enterprise Mvision CD-ROM in your CD-ROM drive.

2. Double-click the icon or the drive label that represents your CD-ROM drive.
3. Double-click the setup.exe program icon to initiate the installation. Note that
when the CD-ROM is installed into the CD-ROM drive, it will automatically start
running if you have the auto-start setting for the CD-ROM turned on. This is the
Windows XP default.
The Welcome Panel appears.

To install MSC Enterprise Mvision:
1. From the Welcome Panel, press the Next button.

2. Choose a destination location, and then press the Next button. A default location
is shown but you can change it to any valid directory on the system.
3. Choose an installation type and then press the Next button. You can choose to
install MSC Enterprise Mvision and/or Integrated Client.
40
4. Select a Web Server to which to install the MSC Enterprise Mvision war file, and
then press the Next button. Selecting Other will allow you to specify a directory
in which to place a copy of the war file.
5. Specify the directory location of the Web Server you chose in the previous panel,
and then press the Next button. This is typically the top level directory (i.e.
C:\Sun\WebServer6.1 or C:\Program Files\Apache Software
Foundation\Tomcat 5.5.)
6. Specify the directory location of an MSC Mvision databanks installation, and then
press the Next button. This defaults to the location of the installed MSC Mvision
databanks if one exists. If there are no MSC Mvision databanks installed, then the
default is the <emv_root>/databases directory that contains a set of demo
databanks. If you specify a directory at this location that is different than the
<emv_root>/databases directory, the setup application configures the databanks
in this directory to run with MSC Enterprise Mvision after the setup application
has completed the file copy phase.
7. Specify the web server context that will be used for MSC Enterprise Mvision
document root (i.e. emv), and then press the Next button.
8. Specify the server ports for the Emv, Admin, and FigureToPngImage servers.
These default to 8023, 8022, 8024, respectively. They can have any numeric value
between 0 and 65536 as long as no other application is using that port.
9. Click the Next button.
10. Specify the server ports for the Emv Monitor and Web Server Java Servlets. These
default to 8021, 8025, respectively. They can have any numeric value between 0
and 65536 as long as no other application is using that port.
11. Click the Next button.
12. Review the settings and verify that the values are specified correctly.
13. Click the Next button to begin the installation process.
If the directory location to the MSC Mvision databanks has been changed from
the <emv_root>/databases directory, the setup application configures the system
to run with these databanks.
14. Select Reboot to complete the installation.
Note: Using the Services Control Panel, the EmvMonitor service can be configured to
interact with the desktop which displays two windows. A Java window
appears that has the EmvMonitor Java application startup information and the
EmvMonitor GUI displays the status of the servers. When the machine boots,
the EmvMonitor service starts automatically. To disable this feature, use the
Service’s control panel to modify the startup of the EmvMonitor service.
CHAPTER 3 41
Installing the MSC Enterprise Mvision Integrated Client

Perform the following steps to install the Integrated Client distribution on Windows
XP.
To install MSC EMV Integrated Client:
1. Insert the MSC Enterprise Mvision CD into your CD drive.
If the InstallShield application does not start automatically, run the setup.exe
executable on the CD.
2. From the Welcome Panel, press the Next button.
3. Choose a destination location, and then press the Next button. A default location
is shown but you can change it to any valid directory on the system.
4. Choose the Integrated Client installation type, and then press the Next button.
Note: You can install MSC Enterprise Mvision and/or Integrated Client.
5. Specify the hostname of the computer on which the MSC Enterprise Mvision
Server is running.
6. Click Next.
7. Specify the port on which the MSC Enterprise Mvision Server is running.
Note: The 2008r1 version of the Integrated Client is only compatible with MSC
Enterprise Mvision 2008r1. Be sure to specify the port for this version.
8. Verify the settings in this screen. Click Next to start copying the distribution.
9. Select Reboot to complete the installation.
Note: To operate the Integrated Client, you must set the following environment
variables in the Systems folder of the Control Panel. For UNIX, perform the
following commands:
• setenv MSC_SDM_IC_PROPERTIES_FILE
<ic_install_dir>/config/MscSdmIC.properties
• setenv LIBPATH <ic_install_dir>/lib:$LIBPATH
42
Installing MSC Enterprise Mvision on UNIX/Linux

This section details the installation of the MSC Enterprise Mvision software on
supported UNIX/Linux computer systems. It is recommended that you read this
section thoroughly before starting the installation.
• Check the system configuration requirements as outlined in Chapter 2 to
ensure your system is ready for a MSC Enterprise Mvision software
installation. If your system does not meet the minimum requirements
outlined in this section, you have to correct the problems before you can
complete the installation.
• You do not have to have root privileges to install the MSC Enterprise
Mvision software. It does require root privileges to make changes to certain
files and to install the licensing software.
• Verify that the Sun Java(TM) System Web Server 6 or higher, or an alternate
Web server is installed.
• Verify that the FLEXlm license system is installed and configured. The
required FLEXlm software can be installed from the delivered CD-ROM.
Installation Procedure
The installation procedure for MSC Enterprise Mvision on UNIX/Linux is a two-step
process:
• The first step extracts and installs all of the required files and executables.
• The second step configures these files for use in your operating environment.
The first step uses an installation script common to all MSC.Software products. From
this single script you can:
1. Mount the CD-ROM drive on the local machine either directly or through an NFS
mount.
2. Unload all the necessary software.
3. Prepare the software for use.
The second step uses configuration scripts included with the installed files for use
with your system.
Installing Using Superuser Privileges

Except for the licensing software, the MSC Enterprise Mvision software can be
installed without using a superuser account or root privileges. Superuser privileges
may be required to overwrite existing Web server configuration files. The software
can be installed anywhere you choose on a machine’s file system as long as the
account you use has write permission to that area.
CHAPTER 3 43
If you decide to use a superuser account for the install, you can be assured that the
mscsetup script described here does not attempt to make any changes except to the
directories you create as part of this install procedure.
Installation of the FLEXlm licensing system does require use of superuser privileges
and does make changes to system directories. Details on this installation are provided
in Installing FLEXlm on page 187.
44
Overview
The following flowchart outlines the steps for installing the MSC Enterprise Mvision
software on a UNIX/Linux system.
Step 1: Mounting the CD-ROM Step 8: Product Licensing

See page 46 Requirements — See page 52
Step 2: Starting the mscsetup Step 9: Installation Review

Installation Utility — See page 47 See page 52
Step 3: Selecting an Installation Device Step 10: Installation Messages

See page 48 See page 53
Step 4: Selecting the Installation Step 11: Setting the User Environment
Directory — See page 49. See page 53
54
Step 12: Verifying the Installation

Step 5: Selecting Products to Install
See page 55
See page 50
Step 13: Installing the Integrated Client

Step 6: Selecting a Product Installation
See page 56
Type — See page 50
Step 7: Setting Application

Prerequisites — See page 52
CHAPTER 3 45
Installing MSC Enterprise Mvision with mscsetup

The mscsetup utility performs all of the steps necessary to install the MSC Enterprise
Mvision software. It creates a log file, mscsetup.log, as a record of all messages,
prompts, and user input. The mscsetup utility also creates a playback file,
mscsetup.pbk.
For a basic interactive installation, MSC.Software recommends executing the
mscsetup utility with no flags or options. For advanced installers, mscsetup offers
the following additional capabilities:
• To generate several identical installations, run in install-only mode and
specify an existing playback file:
mscsetup mscsetup.pbk
• To install a new license.dat file, execute:
mscsetup flex <license.dat_file>
• To obtain usage information on the utility, execute:
mscsetup help
• To display the MSCID, execute:
mscsetup id
This utility is used to generate licenses; see Installing FLEXlm.
mscsetup Command Line Arguments
Command line arguments: Purpose:

-b <installation_dir> Sets the default installation directory.
-f <setup_file> Runs mscsetup from a specified setup file. For
installation of MSC Enterprise Mvision it is recom-
mended that the default setup files (in the CDROM
tools directory) be used.
-l <log_file> Writes the installation log to specified <log_file>.
Default is mscsetup.log.
-m cd:<cd_path> Specifies media type (cd for MSC Enterprise Mvi-
sion) and path to media.
-n Turns off screen handling for text-only scrolling
mode.
-p <playback_file> Writes the playback file to specified
<playback_file>. Default is mscsetup.pbk.
-r <user@node> Sets the user and node for remote installation.

46
mscsetup Command Line Arguments (Continued)
Command line arguments: Purpose:

-t <tmp_dir> Sets the directory mscsetup will use for scratch.
Default is /tmp.
-x Expert mode. Shows menus and prompts with no
explanatory text. Recommended only for users very
familiar with mscsetup.
Step 1: Mounting the CD-ROM

Mounting the CD-ROM may vary depending on the setup of your operating system.
The steps in this section represent default mounting procedures; however, simpler
tools are often available as part of user environment packages, such as the Common
Desktop Environment (CDE) or SGI’s 4DWM. Consult your operating system
documentation for the best method of mounting CD-ROM devices.
To mount the CD-ROM:
1. Create a directory for the CD-ROM (if it does not already exist):
mkdir /CDROM
2. Mount the CD-ROM drive by executing one of the following commands:
HP 11.x: mount -F cdfs /dev/dsk/c0tUd0 /CDROM
where U = the SCSI controller # for the CD-ROM drive
Linux: If your machine does not automatically mount the CD, run
the following command: mount /dev/cdrom /CDROM
Sun Solaris: You do not need to enter a mount command because the
MSC Enterprise Mvision CD-ROM will automatically be
mounted by the Solaris vold daemon. The actual mount
point is specified in the file, /etc/vold.conf, which by
default, is /cdrom/cdrom0. If this directory does not appear
after inserting the CD-ROM, make sure the vold daemon is
running.
IBM: mount -rv cdrfs /dev/cd0 /CDROM
CHAPTER 3 47
SGI: mount -rt iso9660 /dev/scsi/scCdU10 /CDROM
where:
• C = SCSI controller number
• U = CD-ROM unit number
These values can be found by entering the command,
/bin/hinv.
3. Remove the MSC Enterprise Mvision CD-ROM, by entering:

cd <other_dir>
umount /CDROM
Where <other_dir> is any directory, other than /CDROM.
4. Press the Eject button on the CD-ROM drive. On Sun Solaris, enter:
eject cdrom
Step 2: Starting the mscsetup Installation Utility

You do not need to be superuser (root) to run mscsetup. (You might need superuser
(root) access to start FLEXlm on reboot.). The mscsetup utility keeps a log of important
information so it is not necessary to make detailed notes. To execute mscsetup from the
CD-ROM, enter:
<cdrom_dir>/mscsetup
The following information and instructions appear on the screen on an HP

workstation. Other platforms are similar.
Please wait...
MSC Installation and Setup - Introduction
NOTE: You might need superuser (root) privileges to use the default
installation directory /msc.
The following products are available on this delivery:
* EMV (Version)
Please note that new FLEXlm authorization codes are
required to complete the installation of products
contained on this media. NetLS-based licenses used
for previous product versions are no longer valid!
* INTEGRATED CLIENT (Version)
This will install the Integrated Client application utilized in
conjunction with EMV 2008r1.
* FLEXlm Vx.x
48
This will install the FLEXlm License Server and End-

User tools. You should have a file or an e-mail
message containing licensing data before installing
this product.
Do you want to continue (default = Y)? Y
Note: You can terminate the mscsetup program at any prompt command by entering
the character “x” and <cr>.
Step 3: Selecting an Installation Device

When using the mscsetup utility, you must identify the type of media from which you
are installing, and the path to that media.
MSC Installation and Setup - Installation Device Location

1. Install from a local device.
Select this item if the installation device is attached
to this computer, or NFS mounted on this computer.
2. Install from a remote device.
Select this item if the installation CD is attached
to another computer.
X. Completely exit this installation now
Select this item to end this procedure now.
Enter 1, 2, or X (default = 1)? 1
MSC Installation and Setup - Local Installation Device or File
1. Install from local tape.
2. Install from local CD-ROM.
3. Install from local disk file sets.
4. Install from local baseline directory.
R. Return to Installation Device Location menu.
X. Completely exit this installation now.
Enter 1-4, R, or X (default = 2)? 2
Enter the pathname of the local CD-ROM mount point.
Pathname (default = /CDROM)?
Install from /CDROM
Is this OK (default = Y)? Y
Please wait...................................
CHAPTER 3 49
The local CD option assumes that the CD-ROM is available in the same file system as
the installation directory. The CD-ROM must be either locally mounted or NFS
mounted on the same machine as the installation directory.
Step 4: Selecting the Installation Directory

The installation directory is the location where you will install all products. For
example, if you choose /msc as the installation directory, a typical installation would
look like this at completion:
ls -l /msc
drwxr-xr-x root sys 1024 Jul 21 16:33 Gunzip
drwxr-xr-x root sys 1024 Jul 21 16:03 emvxxxxrx
drwxr-xr-x root sys 1024 Jul 21 16:03 icxxxxrx
drwxr-xr-x root sys 4223 Jul 21 16:03 mscsetup.log
The utility also checks the amount of disk space available for that path.
Note: mscsetup requires additional disk space for decompression of the files
contained on the CD-ROM.
MSC Installation and Setup - Installation Base Directory

MSC strongly recommends installing this software in a “common” MSC
product directory to allow MSC products to share common software and
settings.
This can
-Reduce the amount of installation space needed by a product.
-Make future installations easier.
-Reduce the effort needed to administer MSC products.
MSC recommends the standard directory /msc, but alternate choices, such
as /usr/local/msc, are also acceptable.
Enter the pathname of the directory you want to install into,
X to completely exit this installation, or,
? for a list of available filesystems.
Pathname (default = /msc)?
If the directory /msc does not exist, then:

The directory /msc does not exist.
Do you want to create it now (default = Y)?
If the directory /msc exists, then:

Directory /msc exists.
Do you want to use this directory (default = Y)?
When given permission to proceed, the script checks the available space on that disk.
50
Checking available disk space

The size of the file system containing this directory is 939 MB, with 775
MB currently available.
Installing into /msc
Is this correct (default = Y)? Y
Step 5: Selecting Products to Install

After you have entered the appropriate file paths, a menu of all available product sets
on the CD-ROM appears:
MSC Installation and Setup - Select Product

775 MB available in installation directory /msc.
Product Comments
---------------------------- -----------------
1. EMV Standard Application ... Not selected yet.
2. INTEGRATED CLIENT .......... Not selected yet.
3. Adobe Acroread ............. Not selected yet.
4. FLEXlm Vx.x . . . . . . . . Not selected yet.
Enter the number of the product to select or deselect.
X to completely exit this installation.
Enter 1-4, or X (no default)?
Select each product set that you want to install. You must select products one at a time
because each product set selection is followed by appropriate setup questions.
Selecting a product and then choosing a “Custom” installation in Step 6: Selecting a
Product Installation Type, on page 50, allows you to see the full contents of each
product set.
Note: For most licensed products, there is a “Product” listing in mscsetup that
corresponds to each product, module, or databank.
Step 6: Selecting a Product Installation Type

Each product set contains the option for several installation configurations. For MSC
Enterprise Mvision, however, there is only one option for each product. This is called
the Standard installation for each of the available products. The standard installation
options include a description and identifies disk space requirements. For example, the
FLEXlm Application has two options and includes this description:
775 MB available in installation directory /msc.
CHAPTER 3 51
Note: Installation of FLEXlm is NOT required on client systems. A

typical network-licensed site will include one FLEXlm license server
machine to provide runtime license authorization for several client
systems. You should not proceed with installation of FLEXlm unless you
intend to use this system as a FLEXlm license server. You must obtain
licensing data from MSC.Software in order to complete a FLEXlm
installation.
Select an installation option from the list below:

1. Standard Installation.
Install executables and documentation for FLEXlm
Vx.x on Hewlett Packard 9000 systems. 3 megabytes
required.
2. Custom Installation.
Select specific architectural and optional
components to install.
R. Return.
Enter 1, 2, R, or X (default = 1)? 2
The installation type for MSC Enterprise Mvision FLEXlm product sets are:
• Standard includes all files necessary to run the product.
• Custom permits selection of individual components of the product set. You
select individual optional components from menus similar to the product
selection menu.
MSC Installation and Setup - Architectural Components
No. Architectural Component Mode MB

1. Hewlett Packard . . . . . . . . . . .Yes 1
2. Sun SPARC Solaris . . . . . . . . . . No 1
Space required for Architectural Components 1
C. Continue to the Optional Components Menu.
Enter the number of the component to select/deselect,
C to go to the next menu, or
X to exit this installation.
Deselect removes this product set from the “To be installed” listing. The
product selection menu then shows “Not selected yet.”
52
Step 7: Setting Application Prerequisites

Some products include components that require a special setup. For each of these
special components, the script provides additional setup information and prompts
you for required input.
Note: The exact format of the messages and prompts vary according to product
selection and your local environment.
Step 8: Product Licensing Requirements

If you have not already received licenses from MSC.Software, or do not have an
existing license server, the install procedure prompts you to generate a Contract
Amendment. This step creates a file containing the system information that
MSC.Software needs to generate FLEXlm license codes.
MSC Installation and Setup - Product Licensing Requirements

Product...............Licensing....Licensing
......................Methods........Installed
----------------------------------------------
EMV Standard Application . Network ......No
You can generate a contract amendment that can be completed and mailed or
faxed to MSC to request a network license.
Do you want to generate an contract amendment (default = Y)? Y
The MSC Contract Amendment has been written to
/msc/mscauth.txt
Press ENTER or RETURN to continue....
Step 9: Installation Review

Before actually performing the installation, the mscsetup utility reviews your current
selections. You may change the installation source, target install directory, or product
selection.
MSC Installation and Setup - Installation Review

1. Installation Source; Local CD /CDROM
2. Installation Directory: /msc
991 MB total
765 MB available
3. Product Type Size Test
------------------------ -------- ----- ----
EMV Standard Application Standard 82 MB n/a
CHAPTER 3 53
INTEGRATED CLIENT App Standard 83 MB n/a

Adobe Acroread (4.05) Standard 10 MB n/a
FLEXlm Vx.x Standard 4 MB n/a
Enter Y to begin the installation now, or
N to change the installation options.
Is this OK (default = Y)? Y
Step 10: Installation Messages

As the mscsetup utility performs the installation, it issues messages informing you of
its progress.
Note: This information is also recorded in the mscsetup.log file.
In this example, we are installing the MSC Enterprise Mvision core product set
including the Integrated Client, Acrobat components, and the FLEXlm license
management software.
MSC Installation and Setup - Installation

No additional user input will be required.
Writing new playback file, ‘/msc/mscsetup.pbk’
Changing working directory to /msc
Loading installation files. Tue Jul 26 17:32:18 PDT 200x
Using CD-ROM /home/mvlib/delivery/mvship/emvxxxrx
Begin loading files from flexlm/base.tar
Verifying CD load operation...
Begin loading files from flexlm/hpux.tar
Begin loading files from flexlm/htmlman.tar
Begin loading files from hpux/acroread301.tar
Begin loading files from hpux/icxxxx.tar
Begin loading files from hpux/intgclnt.tar
Begin loading files from tools/gunzip.tar
Unpacking installation files. Tue Jul 26 17:33:37 PDT 200x
54
Unpack complete.
Decompressing installation files. Tue Jul 26 17:33:37 PDT 200x
Decompression complete.
Configuring Products. Tue Jul 26 17:38:02 PDT 200x
Configuring FLEXlm Vx.x
Creating directories, setting modes...
Miscellaneous configuration commands...
Updating installation base directory...
Configuring EMV Application

Miscellaneous configuration commands...
Installation complete. Tue Jul 26 17:38:12 PDT 200x
A log of this installation was written to:

/msc/mscsetup.log
Step 11: Setting the User Environment

To complete the installation of the MSC Enterprise Mvision software, a configuration
script must be executed. This script is found in <emv_root>/install/configure. This
script will attempt to modify Web server files, you must have write access to these
files.
Once this script has been executed, you may get unexpected results if you try to rerun
the script with different parameter settings. If you need to rerun this mscsetup
installation script, remove the entire installation directory, and reinstall the product.
The script will complete the configuration by editing the properties files and will
update your Web server files to run with MSC Enterprise Mvision. You will have to
restart your Web server using the updated configuration files to ensure proper
operation.
After executing the <emv_root>/install/configure script, if you have an existing
MSC Enterprise Mvision databank installation, you must configure MSC Enterprise
Mvision to run with these databanks. To run the MSC Enterprise Mvision system with
any databank installation other than the delivered default databank directory
<emv_root>\databases, you must run the <emv_root/install/db_configure script as
part of this installation.
% <emv_root>/install/configure
% <emv_root>/install/db_configure
These configuration scripts, provide detailed user prompts during execution.

CHAPTER 3 55
Refer to Chapter 4 for more information on configuration files and configuring MSC
Enterprise Mvision databanks.
Note: The db_configure script includes all databanks in the databases.txt files. But
only creates Navigation Views in the GroupConfiguration.txt file for
databanks with an associated .mvform file. If you are using an existing MSC
Enterprise Mvision databank installation that contains a form.definitions file
.mvform files can be created for each databank using the mvform_explode script
available in the MSC Enterprise Mvision Builder/ Shareware Utilities.
Step 12: Verifying the Installation

All steps to install and configure the MSC Enterprise Mvision system have been
completed and the software is now ready to use. To verify the installation, type:
% <emv_root>/bin/start_emv_monitor
56
Step 13: Installing the Integrated Client

The steps below explain how to perform the installation on IBM RS/6000, HP-UX,
Linux, and Sun Solaris platforms (collectively referred to as UNIX in the following
instructions).
To install the Integrated Client on UNIX platforms:
1. Insert the MSC Enterprise Mvision CD into your CD-ROM drive. For most UNIX
machines, you will need to issue a mount command to mount the CD. Root
privilege is required to issue the mount command.
2. Run the mscsetup script located in the CDROM directory.
The mscsetup script leads you through the selection of an install directory and
product selection. Answer the questions and provide input as required. The
following steps provide more detailed instructions on the use of the mscsetup.
3. Verify that the product you want to install is included in this install utility. To
continue installation, press <cr>.
4. Select the option representing the location of the installation CD-ROM.
5. Enter the full path to the mount point.
6. Confirm the path with a <cr>.
7. Identify the install directory <ic_install_dir>. MSC recommends installing all
products in a common directory called /msc. If you are running the mscsetup
utility from the directory in which you wish to install, type ‘.’ followed by a <cr>.
8. Verify the <install directory>, using a <cr> for confirmation. If insufficient disk
space exists in this directory for installation, close down the utility and rerun
mscsetup specifying another directory.
9. Review the list of products available for installation. Enter the number
corresponding to a single product you wish to install and press <cr>. The screen
will refresh to allow you to enter other products from the list. Enter C and <cr> to
continue the installation, once all products are selected.
10. Select to install special components, as required and press C and <cr> to continue
the installation.
11. You are given the option to generate a contract amendment requesting a FlexLM
license. Press N and <cr> to bypass this option.
12. Verify the installation details and type Y and <cr> to continue installation.
13. A complete log of the installation is written to the file mscsetup.log in the
<install_dir>.
14. After the install process has completed, execute the
<ic_install_dir>/install/configure_IC script. This script prompts you for the
following.
• Location of the MSC EMV Integrated Client installation directory.
CHAPTER 3 57
• The hostname and port where the MSC Enterprise Mvision Server is
running.
Once the script finishes, the installation is configured.
Note: To operate the Integrated Client, you must set the following environment
variables:
One of the following:
• setenv MSC_SDM_IC_PROPERTIES_FILE
<ic_install_dir>/config/MscSdmIC.properties
• export
MSC_SDM_IC_PROPERTIES_FILE=<ic_install_dir>/config/MscSdmIC.proper
ties
One of the following:

• For AIX platforms:
setenv LIBPATH <ic_install_dir>/lib:$LIBPATH
export LIBPATH=<ic_install_dir>/lib:$LIBPATH
• For Linux & Sun Solaris platforms:
setenv LD_LIBRARY_PATH <ic_install_dir>/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH=<ic_install_dir>/lib:$LD_LIBRARY_PATH
• For HP-UX platforms:
setenv SHLIB_PATH <ic_install_dir>/lib:$SHLIB_PATH
export SHLIB_PATH=<ic_install_dir>/lib:$SHLIB_PATH
58
Configuring the Report Generator

As stated in the Overview, on page 30, the PDF generator uses LaTeX to produce the
report. The configuration of the report generators is very specific to the content of the
property files that call LaTeX functions. The configuration of these files is set during
installation. Use this section as a reference for troubleshooting installation problems.
Two properties in the EmvHardcopy.properties file control the generator:
• hardcopy.latex.batch = GeneratePdfReport.bat
• hardcopy.latex.template = EMVReport.sty
The batch property sets the batch program that converts a LaTeX input file to a PDF
document. The template specifies a LaTeX style file (similar to a CSS file) that controls
the behavior of the LaTeX file.
The GeneratePdfReport.bat File

The binary, EMVReportGenerator (myexecutable in the example), is called using the
batch file, GeneratePdfReport.bat. This file, which resides in <emv_install_dir>/bin,
takes five arguments:
• The EMV install directory
• A newly created temporary directory
• An input xml file describing the material property
• A specified output file name
• A flag described in hardcopy.externaln.flag if the external binary generates
more than 1 report
The command used to execute this file is as follows:
myexecutable “/msc/emv” “/tmp/user1235” “/tmp/user1235/input.xml”
“/tmp/user1235/output.bin” “myflag”
The EmvHardcopy.properties File

Generating a report requires that a series of properties and paths be set in the
EmvHardcopy.properties file in the <emv_install_dir>/config directory.
Each instance of the external report generator (i.e. html, PDF, modified PDF, etc.) requires
a section in the properties file, where hardcopy.external is indexed to represent the
instance (i.e. change external1 to external2, etc.). The example displays the format
for a binary called myexecutable which is called to generate a report of mime-type
text/html using flag, myflag.
Example:
hardcopy.external1.bin = myexecutable
hardcopy.external1.flag = myflag
CHAPTER 3 59
hardcopy.external1.mime = text/html
EMV Examples:
hardcopy.external1.bin = EMVReportGenerator.exe
hardcopy.external1.flag = html
hardcopy.external1.mime = text/html
hardcopy.external2.bin = GeneratePdfReport.bat
hardcopy.external2.flag = pdf
hardcopy.external2.mime = application/pdf
Each instance of hardcopy.externalindex, has a corresponding

FormattedHardcopyExternalindex.html file in the
<emv_install_dir>/html/<user_interface> directory.
It is recommended that you verify the settings within the EmvHardcopy.properties

file:
# This directory is used when writing temporary files
hardcopy.tempdirectory = C:/tmp (Windows) or /usr/local/tmp (UNIX)
# This file is used when generating the PDF report and must be in the
EMV_PATH/bin directory
hardcopy.latex.batch = GeneratePdfReport.bat
(GeneratePdfReport.csh UNIX)
# This file is used by the PDF report and must be in the EMV_PATH/config
directory
hardcopy.latex.template = EMVReport.sty
# This file is used by the HTML report to control the layout and requires
either a URL relative to the servlet or the full URL:
hardcopy.html.template=http://localhost:8080/emv/msc/emv/emvreport.css
60
Installing MSC Enterprise Mvision Databanks

The MSC Mvision databanks are supplied on a separate CD ROM which is delivered
when you purchase any MSC.Software databanks. Follow the procedures in the MSC
Mvision Databank Installation Guide to load the databanks for use by MSC Enterprise
Mvision. We recommend installing the databanks in a directory name
<emv_root>/databases.
Note: If you have not purchased any databanks from MSC.Software, you will find a
directory in the <emv_root> named “databases”. By default MSC Enterprise
Mvision will look in this directory for databanks and support files. This
directory is created when MSC Enterprise Mvision is installed and will contain
sample databanks.
To enable MSC Enterprise Mvision to use MSC Mvision Databanks not located in the
default location, modify the value of the databases variable in the
<emv_root>/config/Global.properties file to reflect the full path to the installed
databases.
CHAPTER 3 61
Updating a Previous Release of MSC Enterprise

Mvision
Installing MSC Enterprise Mvision Version 1.0 on a machine that has a previous
release of MSC Enterprise Mvision already installed requires some modifications.
MSC recommends that you do not install MSC Enterprise Mvision 1.0 in a directory
that contains a previous release. This is important because the location and structure
of the installed software for MSC Enterprise Mvision 1.0 is different from previous
releases. Installing MSC Enterprise Mvision 1.0 in the same directory as a previous
release will damage both releases and neither will function correctly.
Note: Do not install 1.0 in the same directory as a previous release of MSC Enterprise
Mvision.
If you are installing MSC Enterprise Mvision 1.0 on a machine that has a previous
release of MSC Enterprise Mvision, make sure the transition for the users is as simple
as possible. There are several options:
• Install 1.0 and leave the previous installation untouched. The users will have
to change their start-up procedure to access the new directory when they
want to execute 1.0 or they can leave their start-up procedure alone to
execute the previous version.
• Install 1.0 and move the contents of the previous release into its own
subdirectory within the MSC Enterprise Mvision install directory. For
example, if the previous release is 2006r1, then you move the files in
<install_dir> for 2006r1 into a new directory named
<new_install_dir>/emv2006r1.
All users in this case have to change to the new installation directory and
chose between emv2006r1/bin and emv2008r1/bin.
You can simplify transition from one release to the other for all the users at your
facility using a link. After you move the contents of the old release to the new
directory, create a link that points from the old location to the new location in
<new_install_dir>/emv2006r1. When you are ready to switch all the users to 1.0,
change the link to point to <new_install_dir>/emv2008r1.
62
The following table illustrates using this link. In this example, the old version of
MSC Enterprise Mvision is 2006r1 and is installed in the directory /appl/mvision.
Release 1.0 is installed in /appl/msc. The user has /appl/mvision/bin in the PATH
environment variable.
Example of Using Links to Previous Versions
Scenario: Path:
Before 1.0 is installed /appl/mvision/bin/...
After 1.0 is installed. /appl/mvision -> /appl/msc/emv2006r1

Before switch to 1.0 /appl/msc/emv2006r1/bin/...
/appl/msc/emv2008r1/bin/...
After 1.0 is installed. /appl/mvision -> /appl/msc/emv2008r1

After switch to 1.0 /appl/msc/emv2006r1/bin/...
/appl/msc/emv2008r1/bin/...
Depending on your specific site and implementation of MSC Enterprise Mvision,

several HTML templates and/or configuration parameters may require modification
to be integrated into the MSC Enterprise Mvision 1.0 system. For more information,
see Migrating From 2006r1 to 2008r1 on page 90.
Contact your MSC.Software representative for an evaluation and specifications of this
transition.
4 Server Configurations, Utilities, and
Component Information
■ Overview
■ MSC Enterprise Mvision Server Configurations and Configuration
Control Files
■ Features and Utilities
■ Log Files
■ Installing the LDAP Database
■ X Virtual Frame Buffer
■ Migrating From Previous Versions
■ SSL Encryption of the Integrated Client
■ Security Query
64
Overview
This chapter provides detailed information on the required settings for MSC Enterprise
Mvision server configurations and configuration control files. Information is also provided for
system utilities used for administration or operation of MSC Enterprise Mvision. This
information is provided to aid in the administration, customization, and troubleshooting of the
system.
Each server (Emv, Admin, WebServer, EmvMonitor, FigureToPngImage) uses configuration
files found in the <emv_root>/config/ directory. These configuration files are titled “server
name”.properties and are read when the server is started. They provide information on how the
server is configured and where the other servers are located. Options for each server are
specified in the appropriate properties file. These options can be specified on the command line
to override any setting in the associated configuration file. If correctly installed, all of the
“server name” properties will be configured correctly and do not require further modification
to run the standard MSC Enterprise Mvision system.
The EmvMonitor and FigureToPngImage servers are Java applications that require access to a
valid DISPLAY device. Some UNIX workstations may not have access to a graphics display
for the following reasons:
• Workstation does not have a display device
• Workstation does not have access/permission to display device
• User wants to start EmvMonitor and/or FigureToPngImage server(s), and then
logoff from the workstation; thereby losing access to the display
We recommend that the Xvfb (X Virtual Frame Buffer) utility be used as the X server when
starting the EmvMonitor and/or FigureToPngImage servers. Refer to the X Virtual Frame
Buffer section in this chapter for detailed information on this utility.
CHAPTER 4 65
Server Configurations, Utilities, and Component Information
MSC Enterprise Mvision Server Configurations and

Configuration Control Files
EMV Server
The EMV Server-specific configuration parameters (Emv.properties) control:
• Log file format.
• Default legend template for XY-Graphics PNG images and plots and its
location.
• Manipulation of tasks/processes that need to be accomplished before the
execution of MSC Enterprise Mvision.
• Prefix used in the URL to specify that the URL is a JavaServlet request.
• Orbacus parameters for which port the Emv Server listens on and the
number of threads in the thread pool. Do not alter the Orbacus (ooc.boa)
values unless there is a specific reason.
• The encryption algorithms and permissions used when passing data
between the Integrated Client and the EMVServer.
The last line in the file includes the Global.properties file which is a common properties file
used by all servers.
To override parameters in the Global.properties, use the same parameter name found in the
Global.properties files and include the value prior to the include of the
Global.properties file.
EMV Server Configuration Parameters
Parameter: Value:
time_date_stamp_format Time stamp format used in message handler
url_prefix Prefix used to identify the URL as a JavaServlet
request
expanded_search Toggles on/off the use of expanded search in the
export functions. By default it is commented out, as
any value except “no” turns this function on.
trace_idc Turn on/off the tracing of the database engine.
legend_default Default legend template to be used in current user
session
prolog_cmd Executable file to run prior to initializing the
EmvServer. Typically, this is used to stop any export
functions that maybe running and holding on to a port.
66
EMV Server Configuration Parameters
Parameter: Value:
integrated_client_reap_interval Interval between checks for expired Integrated Client
sessions
integrated_client_reap_grace_period Inactive grace period, in seconds, for Integrated Client
sessions.
Integrated Client sessions that do not interact with the
EMV server for the specified length of time, and that
do not respond to the EMV server during a “ping”
operation are purged (logged off) from the system.
integrated_client_expiration Inactivity time in seconds of an Integrated Client
session before it is released (logged-off). The default
is 12 hours.
integrated_client_char_encoding Character encoding to be used when transferring
XML data from the server to the integrated client
application.
ooc.boa.port Port to listen for CORBA connections and requests.
ooc.boa.thread_pool Number of threads to create for the thread pool. Value
must be greater than zero.
ooc.orb.trace_level = 0 Trace level. Value must be non-negative.
emv_encryption_log Specifies the log file name if logging is turned on for
the encryption.
print_encryption_log Toggles on/off the printing of an encryption log. This
option is available by request only for security
purposes.
encryption_only Specifies whether the EMV Server is allowed to
accept unencrypted data from the Integrated Client.
encryption_algorithm Specifies the encryption algorithm to be used by the
Integrated Client when transferring data to the EMV
Server when encryption is turned on by the Integrated
Client. Options: BLOWFISH, DES, 3DES, IDEA,
RC2
legend_position Specifies legend position. The default behavior is for
the legend to be printed below the curve if the length
goes beyond the threshold. Otherwise, it prints next to
the png image.
CHAPTER 4 67
Admin Server
The Admin Server-specific configuration parameters (Admin.properties) control the log file
format and the LDAP server configuration (if its being used). The configuration also specifies
the Orbacus parameters for which port the Admin Server listens on and the number of threads
in the thread pool. Do not alter the Orbacus (ooc.boa) values, unless there is a specific reason.
The last line in the file includes the Global.properties file which is a common properties file
used by all servers.
Global.properties files and include the value before the include of the Global.properties
file.
Admin Server Parameters
Parameter: Value:
time_date_stamp_format Time stamp format used in message handler.
ldap_host LDAP host (blank is localhost)
ldap_port LDAP port (blank is the default:389)
ldap_connection_string LDAP user connection info. This is the information
following the "uid=username," in
"uid=username,o=cm.macsch.com." Note: to get this
string, use the Netscape Directory Server Console,
select the "Create..." button at the bottom right. A
"select org." panel displays. Run the cursor over the
lines and view the strings displayed. Those strings are
the connection info strings the other method is to find
the group that the users are contained in. Then, for each
GROUP, put in ou='***',... from the bottom up. The
root element, put in o='****'. For example: "ou=Emv
Administrators, ou=Groups, o=cm.macsch.com"
EmvMonitor Server
The EmvMonitor Server-specific configuration parameters (EmvMonitor.properties)
control the message handler class, the time and date format, and file name for customizing the
log file format. It also specifies the commands to execute the Emv Server, Admin Server, and
FigureToPngImage Server. Commenting out any of the commands instructs the EmvMonitor
not to start and run that server. Two other parameters control how often the EmvMonitor checks
to see if the servers are running and how often the animation icons are updated to indicate that
the servers are stopped or started.
68
It is important to note that the time to check if the servers are running must be longer than the
total time it takes the servers to get started. (This includes the time required to load all
databanks.)
If the servers don’t respond to the “are you alive” request, the EmvMonitor kills the process
and attempts to restart. This can create an infinite loop of starting and killing the process. If this
occurs, you will see, in the Emv Server log file, that the system keeps starting and never says
ready. This occurs most often because the databanks require more time to load.
The configuration also specifies the Orbacus parameters for which port the server listens on.
Do not alter the Orbacus (ooc.boa) values unless there is a specific reason. The last line in the
file includes the Global.properties file which is a common properties file used by all servers.
Global.properties files and include the value before the include of the Global.properties
file.
EMVMonitor Server Parameters
Parameter: Value:
admin_server_command Fully specified command to start the Admin
Server. Comment out this line to stop the
Admin server from starting.
emv_server_command Fully specified command to start the EMV
Server. Comment out this line to stop the EMV
server from starting.
figure_to_png_image_server_command Fully specified command to start the
FigureToPngImage Server. Comment out this
line to stop the FigurToPngImage server from
starting.
check_interval Interval in seconds to check if servers are
running.
animate_interval Interval in seconds to turn the animation icons
on and off.
emv_message_handler_class Custom message handler class for customizing
the log file output. Provide a Java class that
implements the EmvUtils.MsgListener
interface and put this class in the classpath.
emv_message_log_file_name Message log file name used by default message
handler class.
java_time_date_stamp_format Time-stamp format used in default message
handler.
CHAPTER 4 69
FigureToPngImage Server
The FigureToPngImage Server-specific configuration parameters
(FigureToPngImage.properties) control the message handler class, the time and date
format, and file name for customizing the log file format. This configuration also specifies the
Orbacus parameters for which port the Server listens. Do not alter the Orbacus (ooc.boa)
values unless there is a specific reason.
The last line in the file includes the Global properties file, which is a common properties
file used by all servers.
Global.properties files and include the value before the include of the
Globals.properties file.
FigureToPngImage Server Parameters
Parameter: Value:
emv_message_handler_class Custom message handler class for customizing the log
file output. Provide a Java class that implements the
EmvUtils.MsgListener interface and put this class in
the classpath.
emv_message_log_file_name Message log file name used by default message
handler class.
java_time_date_stamp_format Time-stamp format used in default message handler.
figure_to_png_image_server_ The command line used to initiate the
command FigureToPngServer.
enableChartDebugging Debug Flag. If this flag is set to "true", debugging is
enabled and messages will be generated to inform the
user of the state of the memory and chart creation times
while the system is running. If this flag is set to "false",
no messages will be generated. This value defaults to
"false" - i.e. Debugging is disabled.
logToFile Message Logging Destination. If this flag is set to
"true", the debug messages will be generated into the
normal FigureToPng log file. If this flag is "false",
messages will only be generated to the "stdout"
window. Note that messages sent to "stdout" will only
be visible if the FigureToPng server is started manually
from a command window. The default value is "false"
which results in messages being logged to "stdout".
70
FigureToPngImage Server Parameters
Parameter: Value:
lowMemoryThreshold Low memory threshold. If the amount of free memory
drops below this threshold value the server will
automatically shut down and restart. The default value
for this variable is approximately 15MB.
maximumChartCreateTime Maximum Chart Creation Time. If it takes longer than
the number of seconds specified below to generate a
chart, the FigureToPng server will automatically
restart. This is being done as a stop gap measure for
Boeing because the performance of their server
degrades over time and restarting it resets the
performance back to its original state. The default
value of this variable is a very large number.
chartXsize Chart X & Y size. These values are used to specify the
chartYsize X and Y axis size of the generated chart in pixels. If
these values are not specified they each default to 500
pixels.
Web Server
The Web Server-specific configuration parameters (WebServer.properties) control several
important URLs, the message for customizing the time and date format, and the file name for
customizing the log file format.
The URL parameters control:
• Which HTML page the web server displays
• If the connection to the Emv Server fails
• Which HTML page displays if a session fails to reconnect to the Emv Server
• If an Integrated Client session fails to reconnect to the EmvServer
The configuration also specifies the Orbacus parameters for which port the Web Server listens
on. Do not alter the Orbacus (ooc.boa) values unless there is a specific reason. The last line in
the file includes the Global.properties file which is a common properties file used by all
servers.
CHAPTER 4 71
Global.properties files and include the value before the include of the Global properties
file.
Web Server Configuration Parameters
Parameter: Value:
emv_server_connection_failed_url URL to display when the connection to the
Emv Server is lost or down.
emv_server_reconnect_session_failed_ URL to display when the server fails to
url reconnect a session to the Emv Server.
emv_reconnect_session_int_clt_failed URL to display when the server fails to
_url reconnect to an integrated client session.
emv_message_handler_class Custom message handler class for
customizing the log file output. Provide a
java class which implements the
EmvUtils.MsgListener interface and put this
class in the classpath. See the MSC
Enterprise Mvision Implementation Manual
for more information.
emv_message_log_file_name Message log file name used by default
message handler class.
java_time_date_stamp_format Time-stamp format used in default message
handler.
ie_caching_headers HTTP caching headers for Microsoft
Internet Explorer. Because of the
incompatibility with different Web servers,
Web server host machines, and SSL-enabled
Web servers, the HTTP caching headers for
Internet Explorer have been externalized so
that they can be configured specifically for a
particular installation.
Global EMV-Specific Properties

The Global MSC Enterprise Mvision configuration parameters (Global.properties) control
several parameters that are shared by multiple servers. These parameters are the server CORBA
connection information that a client uses to connect to a server. For example, the Emv Server
uses the admin_server parameter to connect to the Admin Server. This provides a single
source to specify the connection information for all clients. The connection port information
specified must match the ooc.orb.port parameter found in the corresponding server properties
72
file. If the server port parameters do not match, the servers are not be able to communicate. For
example, the Emv.properties file contains the ooc.orb.port property. If it is set to 8023, the
emv_server values must be set to localhost:8023.
The emv_dir parameter defines the installation directory for the MSC Enterprise Mvision
software. If the EMV_DIR environment variable is specified, then that value overrides the
value in the properties file.
You can specify several directory locations in the Global.properties file to allow you to use
existing file locations or distributed files. This capability is particularly important for databanks
that are already installed on the system and can be shared with other applications.
• The emv_platform parameter specifies the operating system platform on
which the Enterprise Mvision server is running (Windows/UNIX).
• The null_value_string parameter specifies the text string to be displayed
when databank attributes with null values are encountered.
• The remote_obj_timeout parameter specifies how much time a request
should take before the system considers the request a failure and terminates
the connection. Currently, this value must be a ‘-1’ due to server connection
failure issues.
• The message_file parameter specifies the messages file for the MSC
Enterprise Mvision messages. You can modify the strings in this message file
as long as the parameter replacement tags remain the same. Note that this is
not a complete list of the strings in the system.
Global Emv-Specific Parameters
Parameter: Value:
admin_server Admin Server host and port.
emv_server Emv Server host and port.
figure_to_png_image_server FigureToPngImage Server host and port.
emv_dir Emv root installation directory.
emv_platform Emv Server platform (Windows/UNIX)
emv_bin_dir Directory containing executable files, scripts, and so
on.
emv_config_dir Directory contains the MSC Enterprise Mvision
configuration files.
emv_databases_dir Directory containing the Mvision databanks, units
files, mapping files, and so on.
CHAPTER 4 73
Global Emv-Specific Parameters (Continued)
Parameter: Value:
emv_html_dir Directory containing the MSC Enterprise Mvision
HTML templates.
emv_security_dir Directory containing the MSC Enterprise Mvision
security files.
emv_external_functions_dir Directory containing the MSC Enterprise Mvision
external functions files.
null_value_string String to use when displaying null databank attribute
values
remote_obj_timeout Time that a CORBA request should wait before
failing with a timeout failure. This value must be -”1”
message_file Message file.
CORBA Server-Specific Properties

This describes the Orbacus parameters included in most of the MSC Enterprise Mvision
configuration files that specify the Orbacus debug flag, configuration information and the
thread pool setting. Do not change these Orbacus parameters unless you have a specific reason.
CORBA Server-Specific Parameters
Parameter: Value:
ooc.boa.port CORBA Server Port that the server listens for requests.
Any client attempting to connect to this server must use
this port. ( 0 <= port <= 65535)
ooc.orb.trace_level CORBA debug information flag to be included in the
running of the server. 1 is on and 0 is off.
ooc.boa.thread_pool Boa thread pool ( n > 0 ).
EMV Server Properties for the Integrated Client

EMV Server specific configuration parameters for the Integrated Client (API access to EMV)
are located in MscIntegratedClient.properties, under the config directory of the
installation. The properties contained within this file primarily control the Integrated Clients’
74
GUI display, and export template mappings of the application. For a detailed description of the
following properties, refer to the MSC EMV Integrated Client Installation and Implementation
Guide.
Server-Side Integrated Client Configuration Parameters
Parameter: Value:
gui.login.user_label Label to be displayed in IC GUI for the
User Name field.
gui.login.password_label Label to be displayed in IC GUI for the
password field.
gui.browser.server_label Label to be displayed in IC GUI for the
server/application name..
gui.browser.server_label_value Value to be displayed in IC GUI for the
server/application name..
<DataSourceName>.<MappingTargetName>.<Te Default Category Name used for
mplateName>,defaultCategory mapping to the specified export target.
Format Flags for Configuration Files

The following format flags from the C programming language’s definition for “strftime” are
valid values for the “time.date.stamp.format” parameter in MSC Enterprise Mvision
configuration files. The message string can be comprised of the following format flags to
generate the desired date and time.
%a
Abbreviated weekday name
%A
Full weekday name
%b
Abbreviated month name
%B
Full month name
%c
Date and time representation appropriate for locale
%d
Day of month as decimal number (01 – 31)
%H
Hour in 24-hour format (00 – 23)
%I
Hour in 12-hour format (01 – 12)
%j
Day of year as decimal number (001 – 366)
%m
CHAPTER 4 75
Month as decimal number (01 – 12)

%M
Minute as decimal number (00 – 59)
%p
Current locale’s A.M./P.M. indicator for 12-hour clock
%S
Second as decimal number (00 – 59)
%U
Week of year as decimal number, with Sunday as first day of week (00 – 53)
%w
Weekday as decimal number (0 – 6; Sunday is 0)
%W
Week of year as decimal number, with Monday as first day of week (00 – 53)
%x
Date representation for current locale
%X
Time representation for current locale
%y
Year without century, as decimal number (00 – 99)
%Y
Year with century, as decimal number
%z, %Z
Time-zone name or abbreviation; no characters if time zone is unknown
%%
Percent sign
The following format flags from the Java programming language’s definition for formatting a
date and time are valid values for the Java_time_date_stamp_format parameter in MSC
Enterprise Mvision configuration files.
The message string can be comprised of the following format flags to generate the desired date
and time.
76
Format Flags
Symbol: Meaning:
G Era designator
y Year
M Month in year
d Day in month
h Hour in am/pm (1-12)
H Hour in day (0-23)
m Minute in hour
s Second in minute
S Millisecond
E Day in week
D Day in year
F Day of week in month
w Week in year
W Week in month
a Am/pm marker
k Hour in day (1-24)
K Hour in am/pm (0-11)
z Time zone
‘ Escape for text
“ Single quote
CHAPTER 4 77
Features and Utilities

EmvMonitor
EmvMonitor ensures that the Admin, Emv, and FigureToPngImage servers are started when the
machine starts and ensures that they are up and running at all times. If one of the servers fails
to respond, EmvMonitor automatically restarts the server that is not responding.
An EmvMonitor Configuration file is located at:
<emv_root>/config/EmvMonitor.properties
The EmvMonitor reads the file at startup to set which servers to start, how often to verify the
status of the servers, and the log file location. See EMV Server on page 65.
EmvMonitor Interface
The EmvMonitor interface as shown on page 78 offers the capability of starting and stopping
the servers, graphically displaying the server status with animated icons, and displaying the
status of the running servers. The EmvMonitor configuration file contains the lines
admin_server_command, emv_server_command, and
figure_to_png_image_server_command. These lines control which servers are started and
monitored by the EmvMonitor. Commenting these lines out with the “#” character disables
those servers from starting. Refer to EmvMonitor Server on page 67.
The EmvMonitor reads the EmvMonitor.properties file at startup. It determines which
servers are to be run and monitored. It first attempts to connect to any existing servers which
are currently running. (Note that if a server is found to be running, then the monitor cannot stop
that server). Any server not already running is started using the command for that server. The
animation icons are started for servers which are running and stopped for servers which are not.
Any connection messages from the servers are listed in the message box and in the
EmvMonitorLog.txt file.
The Start/Stop buttons or the animation icons toggle the state of the server. If the server is
running, the server is stopped and if the server is stopped, it is started.
The animation has a delay of a few seconds that indicates that the server is actually running.
Also, if the Emv Server fails to connect on the first attempt it continues to try until it is
successful. This typically requires a few attempts.
Exiting the Emv Monitor stops all servers which were started with the EmvMonitor. Any
servers that were not started with the EmvMonitor continue to run.
78
EmvMonitor
The default installation of MSC Enterprise Mvision is configured so that the EmvMonitor
interface is displayed when it is executed. For host machines that do not have
access/permission to a display device, you can pass the optional -nogui argument to the
EmvMonitor startup script.
To disable the interface display, for example, use:
<emv_root>/bin/start_emv_monitor -nogui
The Xvfb X Server (Xvfb on UNIX Platforms on page 86) can be used if access to a display
device is unavailable. If the Xvfb X server is used, then the DISPLAY environment variable
must be set (export to ‘hostname‘:1.0) before starting the EmvMonitor.
EmvMonitor Service (Windows XP Platform)

The Emv Monitor starts as a service on the Windows XP platform. It can be installed or
removed using the following scripts:
<emv_root>/bin/install_emv_monitor_service.bat
<emv_root>/bin/remove_emv_monitor_service.bat
These scripts install and uninstall the service and start and stop the service. After the
EmvMonitor is installed as a service, the Services Control Panel is used to stop, start, and
configure the EmvMonitor service.
The EMV monitor GUI and functions are the same whether the EMV monitor executes as a
service or not.
CHAPTER 4 79
Note: Because the EMV monitor starts as a system service, you must make sure that
the system account that started the service has access/privileges to all files and
directories required by MSC Enterprise Mvision. Alternatively, you can start
the EMV monitor service as a user who has access/privileges to MSC
Enterprise Mvision required files and directories from the Windows XP
Services Control Panel.
You can use the Windows XP Services Control Panel to verify that the EMV Monitor service
has been properly installed. Click the EmvMonitor line and then click the Properties... button
(2000), which allows you to set whether the service starts at boot (automatic) and whether it
can interact with the desktop. Allowing interaction with the desktop, the EmvMonitor GUI is
displayed above.
This allows you to control the servers and view their status messages. Turning off the desktop
interaction turns off the interface so that the servers report their messages to the respective log
files only.
Server Monitor
80
EmvMonitor on UNIX Platforms

You can start the EmvMonitor through one of the following methods:
• Automatically start from the inittab file.
• Automatically start using daemons in /etc/rc2.d or /etc/rc.local when
the machine reboots.
• Manually start from the command line.
The EMV installation scripts cannot edit the /etc/rc.local or /etc/inittab files, therefore,
you must edit these files with a text editor. For instructions on editing these files, consult your
system administrator or system documentation.
Starting EmvMonitor with inittab (UNIX platforms)

To start the EmvMonitor using inittab, put the following text on one line in the /etc/inittab
file:
http:2:respawn:<emv_root>/bin/start_emv_monitor [-nogui]
Replace <emv_root> with the directory where you installed EMV.

The -nogui option is an optional command-line argument that forces the EmvMonitor
interface to not be displayed when passed as an argument.
You must remove this line from the /etc/inittab file before you stop the EmvMonitor.
Starting EmvMonitor With the System RC Scripts (UNIX

platforms)
If you use /etc/rc.local, or your system's equivalent, place the following line in
/etc/rc.local:
<emv_root>/bin/start_emv_monitor [-nogui]

The -nogui option is an optional command-line argument that forces the EmvMonitor
interface to not be displayed.
Starting EmvMonitor Manually

You can start EmvMonitor from the command line by entering the following line:
<emv_root>/bin/start_emv_monitor [-nogui]

The -nogui option is an optional argument that forces the EmvMonitor interface to not be
displayed when passed as an argument.
CHAPTER 4 81
Log Files
All of the MSC Enterprise Mvision servers write out log files to the directory
<emv_root>/log. The names of each log file corresponds to the names of the servers which
are generating the messages.
Server Log Files
Server: Log file:

Admin AdminLog.txt
Emv EmvLog.txt
EmvMonitor EmvMonitorLog.txt
FigureToPngImage FigureToPngImageServerLog.txt
WebServer WebServerLog.txt
Message Output Customization (MsgListener Interface)

A feature of MSC Enterprise Mvision is message output customization as described below.
The message handler class provides the ability to customize the log file output by creating a
Java class that implements the MsgListener interface found in the file MsgListener.java.
This file is located at <emv_root>/src/MsgListener.
The interface is a list of method calls which handle error, warning, information, and debug
messages. A method called init is called once when the server starts up and performs
initialization such as opening files, and so on. You can compile your customized
MsgListener. java file and put the resulting class in the classpath. The following is a listing
of the as delivered msgListener.java file.
package EmvUtils;
/**
* Interface to log or displays Emv messages. This is implemented to
* save messages generated by the Emv components (Javaservlets) on the
* web server
*/
public interface MsgListener {
/**
* Error Message output
*/
public void error_msg( String msg_class, String msg_member, String msg );
/**
* Warning Message output
82
*/
public void warning_msg( String msg_class, String msg_member, String msg );
/**
* Information Message output
*/
public void info_msg( String msg_class, String msg_member, String msg );
/**
* Debug Message output
*/
public void debug_msg( String msg_class, String msg_member, String msg );
/**
* Outputs a blank line to the log/display
*/
public void blank_line();
/**
* Init the class
*
* @param emv_root Input - Emv root directory string
*/
public void init( java.util.Properties properties );
};
CHAPTER 4 83
Installing the LDAP Database

A feature of MSC Enterprise Mvision is the ability to use the LDAP (Lightweight Directory
Access Protocol) security system. LDAP enables the Web server to provide security to URLs.
Security may be a concern because the MSC Enterprise Mvision system provides
administrative tools using web pages to update the users, system configuration and databases
while MSC Enterprise Mvision is running.
To install LDAP:
1. Obtain and install an LDAP database.
2. Follow the instructions provided with the software to install the database.
After the LDAP database is installed, you need to update the Web server with database
connection information.
For example, To update the Sun One 6.1 Web server:
1. Connect to the Web Server Administrative Panel and click on the Global Settings
tab. The following panel appears:
Global Settings Tab
2. Enter the hostname and port. You must know where the LDAP database server is
installed and which port it is listening to. For MSC Enterprise Mvision host,
“localhost” and port 389 are the defaults if you have the Sun One 6.1 Web Server.
You must know the Base DN, Bind DN, and Bind password. These parameters are
configured in the LDAP database and must be acquired from its configuration
information.
Restricting Access
After the LDAP database is properly installed and connected to the Web Server, you are ready
to restrict user access to the administrative panel URLs.
84
To create the authorized users that can access the administrative panel URL:
1. Click the Users & Groups tab in the Web server administrative panel.
The following panel appears:
2. Add the user to the system and click the Create User button.
3. Repeat this process for all of the users authorized to use the Administrative tools.
After the users have been added to the system, you can restrict user access for the URLs to only
those users you want to have access to the administrative panel.
To restrict access:
1. From the Web Server Administrative Panel, click the Servers tab so that the list of
servers is shown in the right panel.
2. Click the Manage server button to the right of the server.
The name selected web server’s settings can now be changed.
3. Select the Preferences tab and then select the Restrict Access button.
CHAPTER 4 85
In the right frame, the following page appears:
4. In the Editing list box, either type in or browse to the directory where the
administrative panel is located. For the default installation, this location is
c:/netscape/server4/msc/emv. After the path is selected, click the Edit Access
Control button. This displays the Access Control Rules for the selected path, as
shown below.
Access Control Rules
5. Add new lines and allow users to this path by allowing the user to this path.
Clicking the name anyone can be changed to the user that you entered in the
previous section.
A panel appears below the Access Control panel, which allows you to type in a
name or search for user names.
6. After you have entered name in the subpanel, click the Update button.
The Access Control Section is updated along with the user. Now, only the
specified users can access the path listed. Note that the first line must be set to
Deny Anyone to restrict everyone’s access to this path.
86
X Virtual Frame Buffer

The following utility software is recommended for use with the EMVMonitor described in
EmvMonitor on page 77.
The X virtual framebuffer (Xvfb) is an X server that can run on machines with no display
hardware and no physical input devices. It emulates a dumb framebuffer using virtual memory.
It is an included component of X11R6. The MSC Enterprise Mvision installation on UNIX
platforms other than the AIX, includes this component as part of the install, in the
<emv_root>/Xvfb directory. The installation of Xvfb on the AIX X server is documented in
the last paragraph of this section.
Xvfb on UNIX Platforms

The Xvfb X server can be started through one of the following methods:
• Automatically start it from the inittab file.
• Automatically start it with daemons in /etc/rc2.d or /etc/rc.local when
the machine reboots.
• Manually start from the command line.
The MSC Enterprise Mvision installation scripts do not edit the /etc/rc.local or /etc/inittab
files. Therefore, you must manually edit these files with a text editor. For instructions on editing
these files, consult your system administrator or your system documentation.
Starting Xvfb with inittab (UNIX platforms)

To start the Xvfb X server using inittab, put the following text on one line in the
/etc/inittab file:
http:2:respawn:<emv_root>/bin/xvfb
Replace <emv_root> with the full path of the directory where you installed MSC Enterprise
Mvision.
You must remove this line from the /etc/inittab file before you stop the Xvfb X server.
Starting Xvfb With the System RC Scripts (UNIX platforms)

If you use /etc/rc.local, or your system's equivalent, include the following line in
/etc/rc.local:
<emv_root>/bin/xvfb
Mvision.
CHAPTER 4 87
Starting Xvfb Manually

The Xvfb X server can be started from the command line by entering the following line:
<emv_root>/bin/xvfb
Mvision.
Setting the DISPLAY

Using Xvfb as your X server requires that your DISPLAY environment variable be set
correctly. The shell script (<emv_root>/bin/xvfb) provided with the Enterprise Mvision
installation starts the Xvfb X server with display 1, screen 0 as default arguments. All
applications which use the Xvfb X server must set their display as follows:
C - Shell
setenv DISPLAY ‘hostname‘:1.0
Bourne/Korn - Shell
export DISPLAY=‘hostname‘:1.0
The Xvfb X server is designed in a flexible manner so that it can be started by any user on the
system. Due to security/permission settings on your system, the Xvfb X server might require
root privileges to be started.
Xvfb on AIX (IBM) Platforms

Overview
The AIX X server has been enhanced to support the X Virtual Frame Buffer technology. The
X Virtual Frame Buffer (XVFB) allows the X server to initialize and run without the presence
of any physical graphics adapter. In the past, the X server required one or more graphics
adapters in order to run and would exit with an error if none were present.
Furthermore, in a standard X Window System environment, each 3D application running on a
system must share the same hardware frame buffer. While this is acceptable for viewing clients
locally, it is not acceptable for viewing clients remotely when the graphics windows overlap in
the screen space. This overlap causes rendering to be serialized and slows overall performance.
Using the XVFB, each application has a private 3D-rendering area. Because there is no window
overlap, rendering can take place in parallel. The downside for any locally attached display is
that you cannot see the image on the screen; it must be displayed over the network to be viewed.
In the XVFB environment, an application renders images on a server machine. These images
are then distributed to viewing stations on a network, saved to a database, or used in some other
way. The XVFB environment is convenient for viewing 3D graphics on a low-end system for
casual users.
The XVFB software is supported by AIX 4.3 or later. The XVFB is also supported on the
RS/6000 SP. Install the X11.vfb package, which requires approximately 1 MB of disk space.
Make sure to reboot the system after installing this package.
88
Installing the Xvfb

The XVFB for AIX 5.2/5.3 is installed from the product CDs. Install the following filesets,
where the final digits are release-specific:
• OpenGL.OpenGL_X.dev.vfb.05.01.0000.0000
• X11.vfb.05.01.0000.0000
Starting the XVFB
The XVFB is loaded into the X server with the -vfb flag:
/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :n &
where n is the display number you want to have associated with this instance of the XVFB. This
starts the X server without using any installed graphics adapter and loads the OpenGL
extensions to the X server.
You can also use the xinit command, which starts both the X server and the window manager:
/usr/bin/X11/xinit -- -force -vfb -x abx -x dbe -x GLX :n &
You can also add the -vfb flag to the EXTENSIONS line in your .xserverrc file.
To have the XVFB effective at system boot, have the system administrator add the following
entry in the /etc/inittab file:
xvfb:2:respawn:/usr/bin/X11/X -force -vfb -x abx -x dbe -x GLX :n >
/dev/null
This entry causes the X server to start at system boot time and restart automatically if the server
ever exits or dies.
You can run more than one X server at a time, with the following restrictions:
• You cannot use the COSE Desktop.
• You may use multiple instances of the XVFB X server.
• You can use only a single instance of the X server running to a graphics
adapter.
If you have a system with a graphics adapter, and you want to run one or more XVFB X servers
as well as an X server to your graphics adapter, do the following:
1. Start your X server to the graphics adapter:
/usr/bin/X11/xinit
2. From an xterm/aixterm, start your XVFB server:
/usr/bin/X11/X -vfb -x GLX -x abx -x dbe -force :n &
The display number n must to a number other than the one used with the
graphics adapter.
Starting with Maintenance Level 4330-06, the XVFB can be started with depth 8 or
CHAPTER 4 89
depth 24 (24 is the default). To specify depth 8, include -d 8 on the command line.
If the depth is 8, the colorclass will be 3 (pseudocolor). If the depth is 24, the
colorclass will be 4 (truecolor). These are the only colorclasses supported for
XVFB. Depth 8 is not supported for DirectSoft OpenGL.
Testing the XVFB

Because you cannot see the frame buffer when using XVFB, it is difficult to confirm everything
is working correctly. Fortunately, several X clients ship with AIX that can be used to query and
view window contents, and can be used to help verify that XVFB is rendering the correct
images. These clients include xwininfo, xwd, and xwud.
Verifying that XVFB is Being Used

To verify that an X server is running with the XVFB, use the following command:
/usr/lpp/X11/Xamples/bin/xprop -display sysname:n -root | grep VFB
XVFB_SCREEN(STRING) = "TRUE" <== indicates XVFB is being used
where sysname is the system name and n is the display number for which you are inquiring.
90
Migrating From Previous Versions

Migrating From 2006r1 to 2008r1
All existing HTML pages and configuration files that worked with the MSC Enterprise
Mvision 2006r1.x release will work with the MSC Enterprise Mvision 2008r1 release without
modifications.
The formatted report generation, in available in both PDF and HTML, is a significant
improvement over the original hardcopy capability. However, the original hardcopy is still
available as a printing option in the 2008r1 release. Additionally, the XML intermediary to the
formatted report is also available to allow for additional formatting options. To limit user
access to one or more of the print options, edit the Export.html page in any of the interfaces
to remove unwanted options from the display. The print options are displayed using the
following HTML code, where “Print” is the new formatted HTML and “Standard HTML” is
the previous version.
<INPUT TYPE="BUTTON" NAME="external1" VALUE="Print"
ONCLICK="HardCopyExternal(1)">
<INPUT TYPE="BUTTON" NAME="external2" VALUE="PDF Report"
ONCLICK="HardCopyExternal(2)">
<INPUT TYPE="BUTTON" NAME="external2" VALUE="XML Output"
ONCLICK="HardcopyXMLClicked()">
<INPUT TYPE="BUTTON" NAME="Export to CAE Target" VALUE="Export CAE Data"
ONCLICK="CAEExport()">
<INPUT TYPE="BUTTON" NAME="html" VALUE="Standard HTML"
ONCLICK="HardcopyClicked()">
For more information on the configuration of the Formatted Report Generator,
see
Migrating from 2004r3.2 to 2006r1

All existing HTML pages and configuration files that worked with the MSC Enterprise
Mvision 2004r3.2 release will work with the MSC Enterprise Mvision 2006r1 release without
modifications.
To incorporate fixes and enhancements introduced with 2004, you will need to update the
HTML template files listed below. All existing configuration files should be copied directly to
the 2006r1 installation directory without making any changes. For example, copy the following
files to the 2006r1 directories where they should reside:
<emv_root>/config/GroupConfiguration.txt,
<emv_root>/config/Databases.txt,
<emv_root>/config/InitialUrl.txt,
<emv_root>/security/SecUser.txt,
The properties can also be copied as is, but care should be taken to ensure that the correct host
names and ports are specified in the files.
CHAPTER 4 91
All HTML and HTML template file changes are marked with begin and end change markers
embedded in the files. Each change the following files contains the string of characters “2006r1
Change Begin” to indicate the beginning of a change and “2006r1 Change End” to indicate the
end of a change. The following files in the <emv_root>/html directory contain the changes:
alt_mv3x\cae_export.html
alt_mv3x\datadisplayoptions.html
alt_mv3x\datalist.html
alt_mv3x\export.html
alt_mv3x\hierdatalist.html
alt_mv3x\legendtemplatevalues.html
alt_mv3x\login.html
mv3x\cae_export.html
mv3x\datadisplayoptions.html
mv3x\datalist.html
mv3x\export.html
mv3x\hierdatalist.html
mv3x\legendtemplatevalues.html
mv3x\login.html
simple\cae_export.html
simple\emvloginpage.html
simple\export.html
Migrating from 2004 to 2004 r3.2

MSC Enterprise Mvision has been updated to support relative URL paths as opposed to hard
coded or explicit paths. Therefor all HTML template files have been updated to support this
new feature. If you have custom HTML templates, then you must update your files as demon-
strated in the following examples:
Image tags:
The old image tags required the following text:

<img src=”/emv/msc/images/rainbow2.gif”>
The new image tag should read:

<img src=”../msc/images/rainbow2.gif”>
Anchor tags:
If the old anchor tag provided the following text:

<a href="/emv/EnterpriseMvision?LOGINPAGE=mv3x/Login.html">Link</a>
92
The new anchor tag should read:

<a href="EnterpriseMvision?LOGINPAGE=mv3x/Login.html">Link</a>
Or:
<a href="mv3x/Login.html">Link</a>
Or:
<a href="../../mv3x/Login.html">Link</a>
Note: This text does not include every possible relative path combination, but
serves only as an example of how a relative path works. In addition, you
must make this change globally to all paths in all HTML template files,
including but not limited to, the tag types shown above.
Please see the provided HTML templates provided with your installation for further examples
of changes you may need to make. These files are located in the directory:
Migrating from 2002 to 2004

All existing HTML pages and configuration files that work with the MSC Enterprise Mvision
2002 release will work with the MSC Enterprise Mvision 2004 release without any changes.
To incorporate fixes and enhancements introduced with 2004, you will need to update the
HTML template file listed below. All existing configuration files can be copied directly to the
2004 installation directory without any modification or changes necessary. Simply copy the
<emv_root>/config/GroupConfiguration.txt, <emv_root>/config/Databases.txt,
<emv_root>/config/InitialUrl.txt, <emv_root>/security/SecUser.txt, and so on, to
the 2004 directories where these files reside. The properties can also be copied as is but care
should be taken to ensure that the correct host names and ports are specified in the files.
All HTML-template file changes are marked with begin and end change markers embedded in
the files. Each change in each of the following files contains the string of characters ‘2004
Change Begin’ to indicate the beginning of a change and ‘2004 Change End’ to indicate the
end of a change. The following list of files contain the changes.
From the <emv_root>/html directory:
alt_mv3x\CAE_Export.html
alt_mv3x\CategoryListSelection.html
alt_mv3x\cae_export.html
alt_mv3x\categorylistselection.html
alt_mv3x\criterialistselection.html
alt_mv3x\datadisplayoptions.html
alt_mv3x\error_querysql.html
CHAPTER 4 93
alt_mv3x\login.html
alt_mv3x\querysql.html
alt_mv3x\validatingcriterialist.html- new
alt_mv3x\validatingquery.html- new
mv3x\cae_export.html
mv3x\categorylistselection.html
mv3x\criterialistselection.html
mv3x\datadisplayoptions.html
mv3x\error_querysql.html
mv3x\formattedhardcopy.html
mv3x\login.html
mv3x\logoff.html
mv3x\querysql.html
mv3x\validatingcriterialist.html- new
mv3x\validatingquery.html- new
simple\cae_export.html
simple\logoff.html
uc4\export.html
uc5\export.html
Migrating From 2001 to 2002

The submission of the Advanced Search, Criteria List, and Category pages have changed.
Depending on your interface design and modifications, it maybe necessary to look at the
JavaScript changes that occurred in the QuerySql.html, CriteriaListSelection.html and
CategoryListSelection.html pages.
All existing HTML pages and configuration files that work with the MSC Enterprise Mvision
2001 release will work with the MSC Enterprise Mvision 2002 release without any changes
with the exception of the following files.
Export.html (all interfaces)
The JavaScript function ‘FigureImageClickEvent’ in this file should be
replaced with the same function from the 2002 ‘Export.html’ version.
//------------------------
/**
* Handles figure(curve) click events. This displays the figure(curve) in
* java applet graph display in a new window
*/
function FigureImageClickEvent(dsn,an,view_tag) {
94
window.open( "/servlet/EnterpriseMvision/?EMV_RECONNECT_SESSION=yes&
NEXTPAGE=PlotFigure.html&DSN=" + dsn + "&AN=" + an + "&VIEW_TAG=" + view_tag );
}
It may be necessary, though, to move any installation-modified files from the 2001 to the 2002
installation. These files could include configuration files, databases, external functions,
customized HTML templates, and security files into the 2000 installation directory. This also
includes moving files from the web server’s docs/msc directory to the new 2002 docs/msc
directory.
The configuration files that were most likely changed and should be moved are following:
Databases.txt
GroupConfiguration.txt
InitialUrl.txt
The databases directory most likely contains databases that are specific to your installation.
Compare the contents of the 2001 databases and the 2002 databases directories and move the
desired databases and any associated files and directories.
The external functions might contain customized export functions. Compare the contents of the
2001 external_functions and the 2002 external_functions directories and move any modified
file into the 2002 external_functions directory.
The HTML templates most likely contains customized HTML-template pages specific to your
site. If you have modified either the simple, advanced, or alternate advanced interface, it is
recommended that you compare all of your 2001 files with the 2002 files before replacing your
2001 files over the 2002 files. This will allow you to see any 2002 changes that you may want
to take advantage of in your pages. If you have created your pages in its own subdirectory under
the HTML directory, then simply copy that directory to the 2002 HTML directory.
The security file SecUser.txt in the security directory needs to be moved from the 2001 to the
2002 release. This is if you are using the MSC Enterprise Mvision security system that uses this
file.
The Web server docs directory msc will be renamed to msc.<date-time> during the install
procedure. You most likely will have to copy any pages that were modified for your installation
from this directory to the newly installed msc directory for the 2002 release.
Migrating from 1.0 to 2001/2002

The following changes are required to convert V1.0 files for use in MSC Enterprise Mvision
2001/2002:
• HTML changes to a V1.0 installed advanced interface
(<emv_root>/html/mv3x) HTML pages.
• The same changes are required for the simple interface
(<emv_root>/html/simple).
Without the changes described below, MSC Enterprise Mvision V1.0 files will not function
correctly in the 2001/2002 system.
CHAPTER 4 95
To make the changes:

1. Install MSC Enterprise Mvision 2001/2002 and copy the V1.0 directories from the
<emv_root>/config, <emv_root>/databases, <emv_root>/html, and
<emv_root>/security to the new 2001/2002 <emv_root> directory. Copy the
<netscape_3.6_root>/docs/ to the new <iplanet_4.1_root>/docs/ directory.
This assumes that the recommended Web server iPlanet 4.1 web server has been
installed.
2. All URLs containing the string /iiop must be changed to /servlet. This is due to
the change in the handling of the page requests from Netscape specific’s WAI
interface to an open standard interface provided by JavaServlets. For the HTML
files in the <netscape root>/docs/ and <netscape_root>/docs/msc/emv/
directories, change all URL references from iiop to servlet in the following files.
Index.html
MasterLoginPage.html
EmvLogControl.html
from
/iiop/EnterpriseMvision
to
/servlet/EnterpriseMvision
Note: This is an example of the necessary change. Change all references from iiop to
servlet.
3. For the HTML files in the <emv_root>/html directories, change the references from
iiop to servlet for all files.
Add a hidden field EMV_RECONNECT_SESSION wherever the SESSIONKEY field
exists
from
<INPUT TYPE="HIDDEN" NAME="SESSIONKEY" VALUE="${SESSIONKEY}">
to
<INPUT TYPE="HIDDEN" NAME="EMV_RECONNECT_SESSION" VALUE="yes">
Add the form value EMV_RECONNECT_SESSION=yes to the end of a URL

from
top.DataList.location.href = "EnterpriseMvision?NEXTPAGE=DataL-
ist.html&SESSIONKEY=${SESSIONKEY}" +
to
top.DataList.location.href = "/servlet/EnterpriseMvision/?NEX-
TPAGE=DataList.html&EMV_RECONNECT_SESSION=yes
Add EMV_RECONNECT_SESSION to each form submission (<page>.html). Use the

references to the SESSIONKEY form value to indicate where the
EMV_RECONNECT_SESSION has to be placed. Typically, by completing the
previous two steps, this requirement is fullfilled. When a request does
96
not have the form value EMV_RECONNECT_SESSION=yes set in the request, the
Login.html page is returned.
Remove ${SESSIONKEY} references. It no longer has any effect but causes
no harm.
4. For the following individual files, make the indicated changes:
CriteriaListSelection.html
Add the action to the form tag
<FORM NAME="form" METHOD="POST" ACTION="/servlet/EnterpriseMvision/">
QuerySql.html
Add the action to the form
ColumnHeaderEditor.html
CHAPTER 4 97
ColumnHeaderEditor.html
UnitsSelection.html
DataDisplayOptions.html
GroupSelection.html
DataList.html
Add the MimeFileActionEvent handler
function MimeFileClickEvent(value,dsn,an,iid) {
if (value.substr(0,7) == "http://")
window.open( value );
else
window.open(
"/servlet/AttributeMimeFile/?EMV_RECONNECT_SESSION=yes&NEXTPAGE=PlotFigu
re.html&DSN=" + dsn + "&AN=" + an + "&" + iid );
}
98
Export.html
Add the MimeFileActionEvent handler
function MimeFileClickEvent(value,dsn,an,iid) {
if (value.substr(0,7) == "http://")
window.open( value );
else
window.open( "/servlet/AttributeMimeFile/?
EMV_RECONNECT_SESSION=yes&
NEXTPAGE=PlotFigure.html&DSN="
+ dsn + "&AN=" + an + "&" + iid );
}
Add the SelectedRowsViewsEvent handler that sets the form value
"SELECTEDROWS_0_VIEWS" to the selected view name
function SelectedRowsViewsEvent(obj) {
if (obj.selectedIndex < 0 || obj.selectedIndex >=
obj.options.length) {
alert( "A Property Set or Export View must beselected");
return;
}
ClearExportValues();
document.form.SELECTEDROWS_0_VIEWS.value =
obj.options[obj.selectedIndex].value;
GotoNextPage( "Export.html" );
}
Modify the GotoNextPage function by adding ACTION and PERFORMACTION assign-
ments that set the values to "__EMVTAG_IGNORE_VALUE__"
function GotoNextPage(page) {
document.form.ACTION.value=
"__EMVTAG_IGNORE_VALUE__";
document.form.PERFORMACTION.value =
document.form.NEXTPAGE.value = page;
document.form.submit();
}
Add the ClearExportValues function

function ClearExportValues() {
CHAPTER 4 99
with (document.form) {
// Clear any user settings
for (i=0; i<elements.length; i++) {
if (elements[i].name.substr( 0, 20 ) ==
"EMVVIEWMAPPINGVALUE_") {
elements[i].value = "";
}
}
// Clear any expanded search search setting

for (i=0; i<elements.length; i++) {
if (elements[i].name.substr( 0, 32 ) ==
"EMVVIEWMAPPINGEXPSRCHNAMESTRING_") {
var obj = elements[i];
obj.options[obj.selectedIndex].value =
}
}
}
}
Add the PerformActionPressed function
function PerformActionPressed(obj) {
var s = obj.options[obj.selectedIndex].value;
if (s == "EXCEL" || s == "EXCEL_ALL")
document.form.action =
"/servlet/EnterpriseMvision/Emv_Export_${RANDOMKEY}.xls";
else {
// Validate the unit system. It must be in a
// consistent unit system for export
if (! ValidateUnitSystem())
return;
}
document.form.ACTION.value = s;
document.form.PERFORMACTION.value = s;
document.form.submit();
}
Add the ValidateUnitSystem function
function ValidateUnitSystem() {
100
var s = "${UNITS_0}";
if (s.substr( s.length-11, 11 ) != "_Consistent" &&
s.substr( s.length-11, 11 ) != "-Consistent") {
var msg = "You do not have a consistent Units system selected,
so data values exported may\n" +
"not be correct for your analysis code. Please go back
and change to a consistent\n" +
"Units system, noting that this may require you to change
your numeric queries.\n\n\n" +
"Press 'Ok' to proceed with the action or 'Cancel' to
stop the action.";
return confirm ( msg );
}
return true;
}
Add/edit the following form values. Ensure that they exist in the form during sub-
mission
<INPUT TYPE="hidden"
NAME="SELECTEDROWS_0_VIEWS"
VALUE="__EMVTAG_IGNORE_VALUE__">
<INPUT TYPE="hidden" NAME="ACTION"
<INPUT TYPE="hidden" NAME="PERFORMACTION"
<INPUT TYPE="hidden" NAME="ACTIONDESTINATION"
VALUE="WEB_CLIENT">
Change the block of code that displays the view actions
from
<B>Possible Actions on data</B>${VIEW_0_ACTIONS}</P>
<INPUT TYPE="submit" NAME="PERFORMACTION" VALUE="Perform Action">
<INPUT TYPE="hidden" NAME="ACTIONDESTINATION" VALUE="WEB_CLIENT">
to
<B>Possible Actions on data</B> ${VIEW_0_ACTIONS}
<A HREF="javascript:onclick=PerformActionPressed(document.form.VIEWAC-
TIONS)">
<IMG SRC="/msc/images/bluego.gif" ALT="Go" WIDTH="25" HEIGHT="21" BOR-
DER="0" ALIGN="ABSMIDDLE"></A>
Note that the action/image "bluego.gif" is used to submit the page for this
action. It calls the function PerformActionPressed with the selected view action
passed as an argument.
CHAPTER 4 101
Required Changes for Netscape Enterprise Server

MSC Enterprise Mvision 2001/2002 incorporates the industry standard JavaServlet
technology. The Netscape Enterprise Server 3.6 software is not compatible with this new
technology. You must choose and perform one of the following options:
Continue using Netscape Enterprise Server 3.6

1. You must install and configure the JRun 3.0 software.
2. It is also necessary to turn off WAI for the server using the Netscape Admin
panel->server->Programs->WAI Management.
3. Modify the obj.conf file located in the <netscape_root>/https-<server>/config/
directory. Remove the following lines from this file.
Init fn="load-modules" funcs="EnterpriseMvisionInit" LateInit="yes"
shlib="C:/emv/V1_0/MscEmv.dll"
Init fn="EnterpriseMvisionInit" LateInit="yes" -emv_dir="C:/emv/V1_0"
-figure_to_png_image_server="<server>:8024"
-failed_to_reconnect_url="/msc/emv/Error_FailedToReconnectSession.html"
4. You must restart the Netscape server after these changes are completed.
Migrate to the Netscape iPlanet 4.1 Web Server

To migrate to the IPlanet 4.1 Web server:
1. Install MSC Enterprise Mvision
2. Copy the V1.0 files from the <emv_root>/config, <emv_root>/databases,
<emv_root>/html, and <emv_root>/security directories to the new 2001/2002
directories.
3. Perform changes as outlined in Migrating from 2004r3.2 to 2006r1 on page 90.
After this is complete, the MSC Enterprise Mvision system is ready.
EMV Tag Enhancements and Changes

MSC Enterprise Mvision 2001/2002 incorporates changes to the EMV tags to separate the
property set names from the CAE export targets in the Export.HTML page. These changes have
split the Export.html page into two pages:
• Export.html
• CAE_Export.html
The function of these pages are very similar with the exception that they display property sets
and CAE export targets only. To implement this capability into site-specific customized HTML
pages, see the sample interface files included in the installation for Datalist.html,
Export.html, and CAE_Export.html.
102
In MSC Enterprise Mvision 2001/2002 the EMV tags that set and get cookies have been
removed. You are now required to use JavaScript code to set and get the cookie values in the
HTML pages on the client. See the Sample interface file DataList.html for examples on how to
use JavaScript to set and get cookies.
Using EMV Tags

The behavior or use of other EMV tags has also been modified as follows:
• The SELECTEDROWS_0_VIEWS tag has been enhanced to control what the
tag displays. The EMV tag can now be set to:
SELECTEDROWS_0_VIEWS_PROPERTY or
SELECTEDROWS_0_VIEWS_EXPORT. This displays only the property sets
or export targets for the selected materials respectively. See the Sample
Interface Export.html and CAE_Export.html pages in
<emv_root>/html/mv3x/ for examples on tag usage.
• The VIEW_0 tag has been enhanced with two new variants;
VIEW_0_PROPERTY and VIEW_0_EXPORT. These EMV tags display views
that are property sets or CAE exports respectively. These new tags are
implemented to allow creation of pages that display the property sets or the
CAE export targets only. Note that these tags work together with the new
SELECTEDROWS_0_VIEWS_PROPERTY and
SELECTEDROWS_0_VIEWS_EXPORT tags. See the Sample Interface
Export.html and CAE_Export.html pages in <emv_root>/html/mv3x for
examples on tag usage.
• The EMV GrepDataList and DataList tag has also been enhanced to provide
additional capabilities and control of the material list format parameters.
Refer to the Implementation section for more information.
To configure your existing HTML pages to use the improved GrepDataList
tag, all references to “DATALIST_#” must be changed to
“GREPDATALIST_#”.
To configure the DataList or GrepDataList with the row colors, column
header color, border width, and cell spacing settings, the tags must be
specified before the first display of the DataList tag. See the Sample Interface
Login.html page in the <emv_root>/html/mv3x for an example on tag usage.
Note: These values are specified at login to insure that the settings are set prior to the
DataList display.
CHAPTER 4 103
SSL Encryption of the Integrated Client

MSC Enterprise Mvision 2008r1 provides encrypted programmatic access to data
stored in an Mvision-formatted database via the EMV Integrated Client. Encryption
is facilitated using the CORBA linkage and OpenSSL, an open source commercial
grade full-featured toolkit. OpenSSL is licensed via Apache-style protocols.
To minimize the impact on Client- and Server-side code, the implementation of the
encryption is applied to the data immediately before entering and exiting the orb’s
socket. The encryption is implemented in the CORBA code, which is linked with
OpenSSL cryptographic libraries.
Upon initiation of the IC, the following properties are read in from the
<emv_IC_install_dir>/config/MscSdmIC.properties file, which determine whether
encryption is to be performed:
ic_encryption = no/yes
Initiation of the EmvServer is controlled by properties set in the Emv.properties file,

which resides in the <emv_install_dir>/config/ directory:
encryption_only = no/yes
These properties control whether clients must use encryption. A series of methods
utilize these properties to set the various operational switches and values for the orb
and initialize encryption.
Important: Logging parameters stored in the properties files are disabled. To
enable this feature, contact your MSC representative.
The encryption key is dynamically generated using an OpenSSL command line
statement, which is read in when the EMV server starts. The orb distributes the key on
demand from the clients using a public/private key encryption paradigm to curtail
‘man in the middle’ attacks. Then, using the key, data is symmetrically
encrypted/decrypted by the client/server. The following diagram documents how
the key is sequentially managed.
One – Way Authenticating Key Transport
OpenSSL command
1. Generate a key – the ‘secret’

3. Store the secret key in a pem file
EMV Client ORB EMV Server

2. Server starts
3. Read in the secret key from the pem file
4. Client starts
5. Generate a public/private RSA key
6. Send the public RSA key to the server
7. Receive the client public RSA key
8. Encrypt the secret with the client public RSA key
9. Send the encrypted secret to the client
10. Receive the encrypted key
11. Decrypt the secret with the client private RSA key
13. The secret key is used for symmetric
cryptography
14. The secret key is used for symmetric
cryptography
The ORB is used to transport the secret key to the client

Only the client whose public key was used to encrypt the secret may decrypt it
with its private key
104
Security Query
The Security Query enhancement to EMV has been provided to allow configuration of query
clauses that are added to all EMV queries before they are processed.
A method is provided for the custom authorization code to pass back to EMV a set of query
strings, one per database that is constructed when the user logs in. A security string for each
database may be specified and it shall be applied every data access for that user session and
respective database.
The Security Query is an enhancement to the existing Customizing User Login interface that
is implemented in EmvUserLoginDataAPI.dll.
Please refer to the EMV Installation manual and the section called "Customizing User Login
Environment" to understand the basic concepts of how to utilize this interface.
5 Configuration and User Access Files
■ Overview
■ Using MSC Enterprise Mvision Databanks
■ General Administration Functions
■ Legend Display Customization
■ Configuration Files
■ Customizing User Login Environment
■ URL Utilities
■ Implementing Export Functions for MSC Enterprise Mvision
106
Overview
The MSC Enterprise Mvision information system is a Web-based system that is very
flexible and customizable. User’s access to data and the displayed format of that data
is dependent on various configuration files that control these parameters. The MSC
Enterprise Mvision system provides several utilities to assist in creating and
managing these configuration files.
The information provided in this chapter is intended for the MSC Enterprise Mvision
System Administrator who is responsible for the control and content of the
configuration files that determine user access to the data, the on-screen presentation
of the data, and transfer of the data to external applications.
The next sections provides detailed information on MSC Enterprise Mvision
configuration file requirements and syntax. Included are detailed instructions to how
to use the MSC Enterprise Mvision utilities to create or modify the required files and
how to use the Web-based administration panel to perform online updates of the
system. For installation and system operating instructions, refer to Installing MSC
Enterprise Mvision on page 29. The System Administrator is primarily concerned with
the following files:
• SecUser.txt - Defines username and password.
• UserList.txt - Defines user groups and user default settings.
• Databases.txt - Defines access to databanks and data source cross reference.
• GroupConfiguration.txt - Defines access to and format of databank

information based on group.
• SecQuery.txt - Allows definition of queries that apply globally to a specific
user.
As a general rule, most of the documentation that applies to UNIX platforms also
applies to Linux platforms. Specific differences are noted.
CHAPTER 5 107
Configuration and User Access Files
Using MSC Enterprise Mvision Databanks

Terms
<emv_root> Installed location of the MSC Enterprise Mvision system. Default
location is:
c:/Program Files/MSC.Software/MSC Enterprise Mvision/emv2008r1
(on Windows XP) and /MSC/emv2008r1 (on UNIX/LINUX)
<netscape_root> Installed location of Netscape Server typical location is:
c:/netscape/server4 (on Windows XP) and
/usr/netscape/server4 (on UNIX/LINUX)
Using MSC Mvision Databanks

Original MSC Mvision databanks and the required supporting files are typically
created and maintained on UNIX/Linux platforms using the MSC Mvision Builder
system. You can create original MSC Mvision databanks for Windows XP using the
Batch Builder program provided on the MSC Enterprise Mvision CD (Refer to
Appendix C). You can also create all the required supporting files using any available
text editors. The information presented in this manual is not intended to cover the
building or maintenance of original MSC Mvision databanks. Contact your
MSC.Software sales representative for literature on building databanks and/or MSC
Mvision product information.
Required Databank Content Modification

In MSC Enterprise Mvision, using the latest internet technology, files are retrieved
relative to a base location on the server. Therefore, you may need to modify the
content of an existing Mvision databank before using it with MSC Enterprise Mvision.
The data that may need to be modified are the full text and image attribute values
because these attributes reference external files.
All full text attribute and image values must be relative to the <emv_root>/databases
directory. Absolute directory paths cannot be used. If absolute paths are used in the
databank, these values must be edited and the databank must to be rebuilt to access
this data. Dump the define and input files for the subject databank, edit the input file,
make the paths for the fulltext attributes relative to the databank location, and rebuild
the databank.
Full-text attribute values that are HTML-type files are handled in a different way in
MSC Enterprise Mvision than they are in MSC Mvision Builder. MSC Enterprise
Mvision displays the HTML page in the browser, but if the HTML page references
other objects for display on that page, the request is made to the web Server and not
the MSC Enterprise Mvision server. The client browser is receiving the HTML page
from the Web server just like any other HTML page that is not controlled by MSC
Enterprise Mvision. This means that if a databank-referenced full-text HTML page
108
contains images, the referenced files or images must be in a Web Server docs/
directory and not the <emv_root>/docs/ directory. An alternate method is to change
the databank referenced HTML page references to absolute network paths.
Converting Databanks for Use with MSC Enterprise

Mvision
Most of the information that follows applies to using existing MSC Enterprise Mvision
databanks created on a UNIX platform with the MSC Enterprise Mvision system
running on a Windows XP platform. Many of the same steps are required to relocate
existing MSC Enterprise Mvision databank files for use with MSC Enterprise Mvision
even if you are running on a UNIX/Linux system. If you are using a UNIX/Linux
system most of the following steps apply, but you can link to existing files instead of
copying the file to the same disk space.
All UNIX databanks created with versions of MSC Mvision versions prior to 2004,
except DEC Alpha databanks, must be converted for use with MSC Enterprise
Mvision on Windows XP or Linux. Use the Batch Builder program to rebuild the
databank, (<databank>.des) on Windows XP or Linux using the UNIX-generated
(dumped) define (<databank>.def) and input (<databank>.inp) files. Batch Builder is
provided in the MSC Enterprise Mvision Installation directories. Refer to Appendix C
for more information on the operation of this utility.
The databanks created on a DEC Alpha platform work as generated for the Windows
XP or Linux platform. Copy <databank>.des and its associated files (do not copy the
.index file as it is not used) to the Windows XP or Linux. The file must be copied to the
<emv_databases_dir> directory.
The default name of the <emv_databases_dir> directory is <emv_root>/databases.

This directory can be any valid directory that MSC Enterprise Mvision has access to.
If you do not use the default databases directory, <emv_root>/databases, then you
must modify the emv_databases_dir value in the
<emv_root>/config/global.properties file. If you have an existing databank for
your platform type, you may not need to copy the database or support files. You can
change the path name in the global.properties file. All required files must be in the
same directory. For UNIX/Linux platforms, you can create and use links as required.
Note: When copying files from UNIX to Windows XP or Linux you must use the
correct protocol (usually handled by FTP) because the line terminators for the
different platforms are not compatible.
The basic steps required to convert MSC Enterprise Mvision databanks for use in MSC
Enterprise Mvision are:
1. Copy or convert databank and support files.
2. Create a wrapper for the disclaimer.
3. Modify <emv_root>/config/GroupConfiguration.txt and
<emv_root>/config/databases.txt files.
CHAPTER 5 109
Copying and Converting Databank Support Files

All of the databank support files are text files and are compatible with either Windows
XP or UNIX and Linux.
To copy and convert databank support files:
1. Copy the auxiliary files, <databank>.unt, <databank>.des.mapping or
<databank>.mapping, <databank>.mvform and <databank>.dis to the
Note: The current implementation of MSC Enterprise Mvision does not use the
<databank>.index file. This file does not need to be copied.
2. Copy all directories, containing databank-referenced fulltext and image files into
the <emv_databases_dir> directory, preserving the directory names and structure.
3. Create the <databank>.unt file if one does not exist. You can do this either by
creating an empty file named <databank>.unt or by copying the Mvision.unt (if
it exists) to <databank>.unt. See Step 6 below.
4. Copy the file <databank>.dis to <web_server_root>/docs/msc/emv/disclaimers.
5. The <databank>.mapping files, a text file, are the same on Windows XP, UNIX and
Linux, so no changes should be required. An exception is if the file is named
<databank>.des.mapping on the UNIX platform. It must be renamed
<databank>.mapping for use in MSC Enterprise Mvision.
6. The <databank>.unt files on Windows XP, UNIX and Linux are the same. No
changes should be required. An exception is if the unit system name in the UNIX
file contains spaces. These spaces must be removed or replaced with a symbol like
“_” for use by the MSC Enterprise Mvision system. It is further recommended
that you add a default unit system name to the file. This is a line that identifies the
“as created” unit system and does not perform any conversions. This default unit
system will inform the user what unit system the data was created in rather than
presenting the user with the generic term “default”.
7. Create a <databank>.dis disclaimer wrapper for each databank by copying one of
the existing *.jsp files and replacing the databank name in the line:

JavaScript in the MSC Enterprise Mvision HTML template DataList.html dis-
plays this <databank>.jsp using the JavaScript function DisplayDis-
claimer(doit). A cookie is also set so that the disclaimer is displayed once per
calendar day. Refer to Creating Databank Disclaimers on page 122 for more infor-
mation.
8. Copy the UNIX version of the form.definitions file or the <databank >.mvform file
associated with the databank being converted and to the <emv_databases_root>
directory.
110
9. Add all of the subject databank names to the listing in the

<emv_root>/config/Databases.txt file. The Databases.txt file contains a listing
of all databanks that can be accessed (opened) by MSC Enterprise Mvision. Each
line is a comma-separated list of “Datasource” name, “Databank” name, and
initial cache size.
• The first column is the datasource name. This is the name which appears in
all selection lists and is displayed on the pages. The datasource name can be
any combination of alpha or numeric characters, but cannot contain spaces.
• The second column is the databank name and must exactly match the file
name of the databank as referenced in the <emv_databases_dir> directory.
• The third column is the initial cache size for the databank in kilobytes. This
can be any value between 1-100,000. If the cache size is not specified, or is 0,
a default value of 8000 kilobytes is set.
Example of Databases. txt file format:
fiber,fiber.des,250
mil-handbook-5, mil5.des, 1000
heat, thermal.des
Edit the <emv_root>/config/Databases.txt file to include all of the databanks
you want to access.
10. Run the <emv_root>/bin/FormDef2GrpConfig program as described in Creating
GroupConfiguration.txt From a Form File on page 113 to convert a
form.definitions file to a GroupConfiguration.txt file. These files serve
analogous functions. The GroupConfiguration.txt file may contain the contents
of several form.definitions files.
Configuring MSC Enterprise Mvision for Full Text and

Image Attribute Viewing
Viewing of full text and image attribute values in the MSC Enterprise Mvision system
is handled by the browser. To access and view documents or images that are
referenced by "full text" or "image" attributes in an MSC Enterprise Mvision databank,
both the server and the client must have the same MIME type registered and an
appropriate viewer application must be accessible on the client.
MSC generally recommends using "in-line plug-ins" for the viewing of documents
and images. This provides a consistent and fluid viewing process. If a plug-in is not
available for a specific document or image type the browser can be configured to use
a third-party application. If the client is currently using an existing application to view
MSC Enterprise Mvision referenced documents or images, the client browser can be
reconfigured to invoke a different application.
CHAPTER 5 111
To obtain "in-line plug-ins" for viewing specific documents or image types in the
Netscape browser:
1. Access the Netscape home page http://home.netscape.com.
2. To download the required software in the "Web Tools" section, select "Plug-ins".
3. On the page that appears, select "Search Plug-ins" to search for and download
plug-ins that are currently available for your specific platform, mine type, and/or
file extension.
For the Internet Explorer browser, you have to search the Web for the appropriate
plug-ins.
Most file types (MIME types) are predefined in the supplied version of the MSC
Enterprise Mvision web server software. For special (company-specific) or
non-standard file types, you may be required to set the MIME type /application
association as detailed below.
For Windows XP, to determine if the MSC Enterprise Mvision referenced document or
image type is viewable using the current configuration:
1. Locate the file in the <emv_databases_dir> directory .
2. Double-click the file name.
If the document or image displays correctly, then your existing configuration is
correct for this file type.
To determine the MIME type for a file or image on an Windows platform using Internet
Explorer:
1. Select Tools/options/file types from the menu bar in the window in which the
filename is displayed.
2. Find the file type that you want to view and note the associated MIME type for this
file setting.
3. If the document or image is not viewable, select “New” and follow the instructions
for your system to add a new MIME type to the registry. You must also specify an
application to be used on the client side to display the file. This setting is only for
local use and is not transmitted with the file. When a document or image is
displayed in MSC Enterprise Mvision, the system transmits the file with the MIME
type specified on the server for the specific filename extension being transmitted.
4. To determine the MIME type for a file or image on a UNIX/Linux platform
Display the file or image in your Netscape browser (that is, file:/<full path to
file>) popup menu and select “view page info”. If the MIME type is recognized,
it is stated in the page information.
5. If the MIME type is not recognized, select Edit/Preferences.
6. When the dialog appears, select Navigator/Applications.
112
7. If the document or image is not viewable (listed), select New and follow the
instructions for your system to add the new MIME type. You must also specify an
application to be used on the client side to display this file. This setting is only for
local use and is not transmitted with the file. After you have determined the
current MIME type for the file or image, you must add this MIME type to the
<emv_root>/config/MimeTypeMappings.properties file in order to pass the MIME
type to the client. This typically is one line, the format of the file is <filename
extension>=<mime type>.
You must provide the MIME type and the associated application to your clients to
correctly configure the client browser to recognize the file type received. The client can
then configure the browser to recognize this MIME type and associate it with the
appropriate plug-in or application. Repeat this process for each file name extension
that is referenced in the MSC Enterprise Mvision databank.
To display any document or image that is currently contained in an MSC Mvision
databank and displayed via the MSC Mvision Builder or Evaluator product on a UNIX
platform, the user must configure the client browser to recognize the transmitted
MIME types and invoke the appropriate application.
• For "full text" attributes UNIX/Linux users must configure the browser to
associate the "application" specified in the current MSC Mvision "helpers"
file to the transmitted MIME type.
• For "image" attributes the appropriate "plug-in" must be installed and
associated with the transmitted MIME type.
If an appropriate plug-in is not available, the browser can be configured to
use any application that can be accessed by the client machine. The
application "XV" displays all image types which are currently displayable in
the MSC Mvision Builder and Evaluator product and can be downloaded
from http://www.trilon.com/xv/xv.html.
After installing this application on a UNIX/Linux client, this application can
be invoked through the Netscape browser by setting the
Preferences/Navigator/Applications command to "xv %s" for the required
MIME type and filename extension.
If a plug-in or application is not available to view the MSC Enterprise Mvision
databank as stored image, you can use the UNIX MSC Mvision Builder or Evaluator
"mv_image" program to translate the image to a browser-viewable image type before
copying the image file to Windows XP platform.
To translate an image from one format to another:
1. Choose the appropriate program from the <MSC Mvision_install_dir>/bin
directory.
2. Execute the program with the filename of the image you want translated as the
argument.
CHAPTER 5 113
For example, <MSC Mvision_install_dir>/bin/ppmtogif <filename>.ppm would

convert the specified ppm to a GIF image which is viewable using the browser "in line
plug-in". Images can also be translated using the above mentioned "XV" program.
Load the required image and save the image to a browser viewable format.
If the current images in a MSC Mvision databank are of <filename>.mv image format,
then these images must be translated to a browser viewable image. There are no
applications available for the UNIX/Linux or Windows XP platforms to view these
images.
To translate a <filename>.mv image on a UNIX platform:
1. Execute <MSC Mvision_install_dir>/bin/mv_image.
2. Select an image format that is compatible with your browser.
If the image format and/or filenames for an existing MSC Mvision databank are
changed, the filename references in these databanks must be changed. You can rebuild
these databanks using the Batch Builder program, dump a define and input file for the
subject databank, edit the filename in the input file and rebuild the databank. Refer to
Getting Started with Batch Builder on page 212.
Creating GroupConfiguration.txt From a Form File

To convert an existing form.definitions file to an MSC Enterprise Mvision
GroupConfiguration.txt file, you have the option of using one of the following utility
programs to perform the conversion:
• FormDef2GrpConfig - Interactive GUI application (JAVA) (not available on
SUN)
• FormDef2GrpConfigPrompt - Script file which prompts the user for arguments
(UNIX/Linux only)
• FormDef2GrpConfigCmdLine - User specifies arguments to utility on the
command line
Performing the conversion using any of the above utilities produces identical results.
Note: The <emv_root>/config/Databases.txt file must be modified to include the

subject databank prior to executing these programs. See Step 9 in Copying and
Converting Databank Support Files on page 109.
114
The first option is executing the Java application program

<emv_root>/bin/FormDef2GrpConfig, which displays a dialog as shown below. Follow
the detailed instructions for inputs and operation.
Form Definition to Group Config File Translator
1. Specify the full path for the form.definitions file to be converted. Clicking the
“…” button displays a file selection box for browsing.
2. Specify the full path for the <emv_root>/config/Databases.txt file which
contains the mapping for the data source name and the actual databank location
relative to the <emv_databases_dir> directory. The databank name that the
form.definitions file references must be listed in the Databases.txt file before
running this utility. Clicking the “…” button displays a file selection box for
browsing.
3. Specify the full path for the databank directory, <emv_databases_dir>. All
databanks referenced in the form.definitions file must be relative to this directory.
The Databases.txt file maintains the reference between the data source names
used in the GroupConfiguration.txt file and the actual physical location of the
databanks. The databank names used in the form.definitions file must match
the databank names in the Databases.txt file exactly.
The one exception is when a wildcard is used in the databank name in a form
within the form.definitions file being converted. The utility FormDef2GrpConfig
automatically creates a Navigation View for each databank that matches a form
with a wildcard databank name. For example, if the databank name m*.des is
present in a form.definitions file the same Navigation View is repeated for each
databank name in the Databases.txt that matches (that is, every databank name
that begins with “m”).
CHAPTER 5 115
Note: If a <filename>.mvform is to be converted, the line version: "3.0"; must be

added as the first line in the file prior to conversion.
4. Specify the name of the output file which is typically GroupConfiguration.txt.
Caution: This file is overwritten without you being prompted so be careful when
specifying this filename.
5. Click the Convert button to start the conversion process. Examine the status
messages of the conversion. All messages should be reviewed and any errors
corrected.
Note: The databanks that are opened during the conversion process are not closed
until the utility FormDef2GrpConfig is terminated. Therefore, rerunning the
utility repeatedly without closing the form opens all the databanks several
times and possibly causes memory overload problems. To clear these memory
errors, terminate and restart the FormDef2GrpConfig utility.
6. To include the contents of the Group Configuration file generated in the previous
step in the current MSC Enterprise Mvision system, modify the generated
GroupConfiguration.txt file as required. Review the contents of the new
GroupConfiguration.txt file and rename the groups or paste the contents of the
Navigation View into an existing Group. Verify that the Navigation View names
are unique within each Group.
7. If a new Group is being created, add the new Group name for the appropriate
users listed in the <emv_root>/config/UserList.txt file. These are the only users
who are to be allowed access to this new Group. If the Group is the first Group
listed for the user in the UserList.txt file it becomes that user’s default Group
(the initial Group for the user when he logs on to MSC Enterprise Mvision). See
General Administration Functions on page 124 for more information.
8. For the above changes to take effect, it is recommended that the MSC Enterprise
Mvision server be stopped and restarted, which causes the appropriate
databanks, views and groups to appear in their respective Selection Lists for all
users. You can also invoke changes to the configuration settings using the
Administrative Panel Interface. Refer to Starting the Administrative Panel
Interface on page 181. This invokes the changes online and alerts the active
clients. After the active users log out and then log in again, all changes are in
effect.
9. After the server has restarted, verify that no errors occurred by viewing the
<emv_root>/logEmvLog.txt file. Look at the end of the file for the last “Starting
EMV ... line and verify that no error messages exist.
Steps 6-9 above applies regardless of which utility is used to modify the configuration
files.
116
Note: When starting the MSC Enterprise Mvision server and loading databanks
using the EMV monitor, (all databanks are loaded when the server starts) you
may be required to increase the “Check_interval” value in the
<emv_root>/config/EmvMonitor.properties file to allow the system enough
time to load all the databanks. This also requires you to exit and reinitiate the
EMV monitor program.
The next option (for UNIX/Linux only) is executing the script file
<emv_root>/bin/FormDef2GrpConfigPrompt . This is identical to the graphical
Interface with no browsing capabilities. The function of this program prompts the
user for the following information:
• Location of the form.definitions file. You must enter the full path for the
form.definitions file, when prompted.
• Location of the Databases list file (Databases.txt). You must enter the full
path for the databases.txt file, when prompted.
• Location of the databank directory. You must enter the full path for the
databank directory, which contains all the appropriate databank and
support files when prompted.
• Location of the Group Configuration (GroupConfiguration.txt). You must
enter the full path for the GroupConfiguration.txt file when prompted.
The third option is to use the <emv_root>/bin/FormDef2GrpConfigCmdLine utility,
which requires the following command line specified arguments when invoking the
utility:
• Location of the form.definitions file, including path, specified as:
-form_file <form_def_file>
• Location of the Databases list file, including path, specified as:
-databases_file <db_file_list>
• Path name of Databank directories specified as:
-databases_path <db_path>
• Location of the Group Configuration, including path, specified as:
-group_config_file <group_config_file>
The following is an example command for invoking the FormDef2GrpConfigCmdLine

utility:
FormDef2GrpConfigCmdLine \
-form_file /tmp/form.definitions \
-databases_file /Emv2008r1/config/Databases.txt \
-databases_path /Emv2008r1/databases \
-group_config_file /Emv2008r1/config/GroupConfiguration.txt
CHAPTER 5 117
Creating Default Navigation Views for MSC Enterprise

Mvision
MSC Mvision Builder or Evaluator, automatically generates a default form for any
databank for which one does not exist. This dynamic capability does not exist in MSC
Enterprise Mvision. A utility is provided which generates the same type of default
view for any databank that can be opened in MSC Enterprise Mvision. To create a
default Navigation View, you have the option of using one of the following utility
programs:
• AddDefaultDbNavView - Interactive GUI application (JAVA) (not available on
SUN)
• AddDefaultDbNavViewPrompt - Script file which prompts user for arguments
(UNIX/Linux only)
• AddDefaultDbNavViewCmdLine - User specifies arguments to utility on the
command line
Creating a default navigation view using any of the above utilities, produces identical
results.
Note: The <emv_root>/config/Databases.txt file must be modified to include the
subject databank prior to executing these programs. See Step 9 Copying and
Converting Databank Support Files on page 109.
The first option executing the Java application program
<emv_root>/bin/AddDefaultDbNavView , displays a dialog as shown. Follow the
detailed instructions for inputs and operation.
118
Default Navigation View Generator
1. Specify the full path for the databank to create a default Navigation View.
Clicking the “…” button displays a file selection box for browsing.
2. Specify the full path for the <emv_root>/config/Databases.txt file, which
contains the mapping for the data source name and the actual databank location
relative to the <emv_databases_dir> directory. The databank name entered in the
database selection must be listed in the Databases.txt file. Clicking the “…”
button displays a file selection box for browsing.
3. Specify the full path for the <emv_root>/config/GroupConfiguration.txt file.
This is the file where the Navigation View is added. Clicking the “…” button
displays a file selection box for browsing.
CHAPTER 5 119
4. Specify a Group to which the new default Navigation View is to be assigned.

Clicking the “…” button displays a dialog which lists the existing Groups found
in the GroupConfiguration.txt file specified in the previous selection. You can
select an existing group listed in the GroupConfiguration.txt file or enter a name
for a new group. Select a group name and click the OK button.
Group Selection Dialog Box
5. Click the Start button to create the default Navigation View. Examine all the
status messages for the default view creation. All messages should be reviewed
and any errors corrected before proceeding to the next step. Also review the
modified file to verify the Navigation View creation and group assignment.
6. For the changes to take effect, we recommend that the MSC Enterprise Mvision
server be stopped and restarted. When the MSC Enterprise Mvision server is
restarted, the new default Navigation View appears in the selection list for the
assigned Group. You can also invoke changes to the configuration settings using
the Administrative Panel Interface. Refer to Starting the Administrative Panel
Interface on page 181. This invokes changes online and alerts the active clients.
After active users logout, then log in again, all changes are in effect. The above
applies regardless of which utility is used to modify the configuration files.
<emv_root)/Log/EmvLog.txt file. Look at the end of the file for the last “Starting
EMV...” line and verify that no error messages exist.
Steps 6-7 above apply regardless of which utility is used to modify the configuration
files.
120
The next option (for UNIX/Linux only) is executing the script file
<emv_root>/bin/AddDefaultDbNavViewPrompt. The function of this program is
identical to the graphical interface with no browsing capabilities. The script prompts
the user for the following information:
• Location of the Databank file. The user must enter the path for the databank
file to include the .des extension when prompted.
• Location of the Databases list file(Databases.txt). The user must enter the
full path for the databases.txt file when prompted.
• Location of the Group Configuration file (GroupConfiguration.txt). The
user must enter the full path for the GroupConfiguration.txt file when
prompted.
• Group name to assign the default Navigation View. The user can enter a
valid Group name listed in the (GroupConfiguration.txt) file or a new group
name, when prompted.
The third option is to use the <emv_root>/bin/AddDefaultDbNavViewCmdLine utility
that requires the following command-line specific arguments when invoking the
utility:
• Location of the Databank file, including path, specified as:
-database <db_file>
• Location of the Databases list file, including path, specified as:
-databases_file <db_file_list>
• Location of the Group Configuration, including path, specified as:
-group_config_file <group_config_file>
• Valid group name from the file specified for the -group_config_file
argument
The following is an example command invoking the AddDefaultDbNavViewCmdLine
utility:
AddDefaultDbNavViewCmdLine \
-database /Emv2008r1/databases/fatigue.des \
-group_config_file /Emv2008r1/config/GroupConfiguration.txt \
-group Design
Note: The GroupConfiguration.txt file must be writable for this operation to be

successful. If the GroupConfiguration.txt file is not writable, then the
AddDefaultNavView utilities issues an error message and exits.
CHAPTER 5 121
Validating the Group Configuration File

Due to the complexity and size of the Group Configuration file, a validation tool is
available to verify the syntax of the file and also the validity of the database
specifications, database expressions, and queries specified for each navigation view.
To run the Group Configuration File validator, you have the option of using one of the
following utility programs:
• GroupConfigValidator - User specifies arguments to this utility on the
command line
• GroupConfigValidatorPrompt- Script file that prompts the user for
arguments (UNIX/Linux only)
The first option runs the <emv_root>/bin/GroupConfigValidator program which is a
command line program. The following demonstrates how to use this application in
command line mode.
GroupConfigValidator \
-databases_file <databases_txt_file> \
-group_config_file <group_config_file> \
-databases_dir <databases_dir> \
-verbose
The following explains the parameters for the GroupConfigValidator.

• databases_file - Specifies the full path to the Databases.txt file. This file is
typically located in the <emv_root>/config/Databases.txt file. This file
contains the mapping for the data source name and the actual databank
location relative to the <emv_databases_dir> directory.
• group_config_file - Specifies the full path to the Group Configuration file
that is to be validated. This is typically located at:
<emv_root>/config/GroupConfiguration.txt.
• databases_dir - Specifies the full path of the directory where the databases
are located. This is typically <emv_root>/databases.
• verbose - Displays more information during the execution of the
GroupConfigValidator utility. This is useful when an error is occurring
about the configuration of the files or system.
The following is an example command invoking the GroupConfigValidator utility:
GroupConfigValidator \
-group_config_file /Emv2008r1/config/GroupConfiguration.txt \
-databases_dir /Emv2008r1/databases
-verbose
When this application is run, it validates the syntax of the file and reports any errors
with the associated line number and actual line. Validation of database information,
such as the data source for a navigation view, column headers, and queries, is also
validated and reported with the associated line number and actual line. This program
122
should be run after making any changes to the GroupConfiguration file and all
reported errors should be addressed prior to incorporating the GroupConfiguration
file with MSC Enterprise Mvision.
Creating Databank Disclaimers

The disclaimer files (<databank>.dis)from a MSC Enterprise Mvision Builder or
Evaluator Installation can be used in MSC Enterprise Mvision without modification.
But a new <databank>.jsp file that includes the <databank> name is required.
When a databank is opened in MSC Enterprise Mvision, the DataList.html template in
the <emv_root>/html/ directories is called and contains a JavaScript function that
displays the Databank disclaimers from the
<emv_webapp_root>/msc/emv/disclaimers directory. The disclaimer process uses two
files that produce the displayed disclaimer page; the <databank>.dis disclaimer file
and a <databank>.jsp file.
The <databank>.jsp file is a wrapper (i.e. preprocessor) for the actual <databank>.dis
file. The web server includes the <databank>.dis text file in the <databank>.jsp file.
Using this technique, the <databank>.dis file does not have to be changed to apply
HTML formatting.
The following is an example of the required <databank>.jsp file:
<HTML>
<HEAD>
<TITLE>Databank Disclaimer</TITLE>
<LINK REL="STYLESHEET" HREF="/msc/emv/Disclaimer.css">
</HEAD>
<BODY>
<P ALIGN="center">
<PRE>
<%@ include file="databank.dis" %>
</PRE>
<FORM>
<CENTER>
<P ALIGN="CENTER"><INPUT TYPE="BUTTON"
NAME="Close" VALUE="Close"
ONCLICK="javascript: window.close()">
</P>
</CENTER>
</FORM>
</BODY>
</HTML>
To incorporate a MSC Mvision disclaimer file in the MSC Enterprise Mvision, copy the
<databank>.dis file to the <emv_webapp_root>/msc/emv/disclaimers directory. Copy
any existing .shtml file in the disclaimers directory to <databank>.jsp where the
databank name matches the >databank>.dis name you added. Change the “<%@
include” line in the new.jsp file to match the databank.dis file you added.
CHAPTER 5 123
If the <databank>.dis and <databank>.jsp files do not exist, the JavaScript in the
DataList.html template attempts to open a page that does not exist and the following
error message displays in a new window:
The DataList.html template file can be modified to search for files in directories other
than <emv_webapp_root>/msc/emv/disclaimers or the disclaimer action can be
disabled by modifying the search paths or actions in the JavaScript function in the
DataList.html template page.
124
General Administration Functions

For both the Windows XP and UNIX/Linux platforms, the general procedures and
actions for configuring and invoking the system configuration files and operating
parameters are identical, except as noted.
Add/Modify a User
If using the standard MSC Enterprise Mvision security method, to add a user to the
MSC Enterprise Mvision system, you must modify the UserList.txt and the
SecUser.txt files. See UserList File on page 142 and Security Files on page 144 for a
description of the file content and structure. Then, you must stop and restart the MSC
Enterprise Mvision server; or update the system using the Administrative Panel
Interface. Refer to Update Group Configuration on page 183.
To add a new user to the MSC Enterprise Mvision system, you must edit the
<emv_root>/security/SecUser.txt file.
Editing SecUser.txt
To edit the SecUser.txt file:
1. Open the file <emv_root>/security/SecUser.txt for editing.
2. Add the new user to this file. Add the User ID, Password and a required zero to
the file. These values are comma separated. See Security Files on page 144 for
details on file content and format.
3. Close and save the SecUser.txt file.
Editing SecQuery.xml
To edit the SecUser.txt file:
1. Open the file <emv_root>/security/SecQuery.xml for editing.
2. For each User ID specified in the SecUser.txt file, you may add an unlimited
number of queries using Mvision query syntax for each database. Set the
dbRestricted value = 'true' to apply the specified constraints to the EMV
Security functionality. See Security Files on page 144 for details on file content
and format.
3. Close and save the SecUser.txt file.
Editing UserList.txt
To add a new user or modify defaults or access for existing users:
• Edit the file: <emv_root>/config/UserList.txt.
CHAPTER 5 125
The file UserList.txt contains four columns of data for each user, as shown
in the example below:
Example Columns of Data
User ID: Default group: Default units: Allowed groups:

LoisLane user US user
ClarkKent super SI user, super
• User ID - The User ID column contains the name that the user must type in
when logging into the system. This name must exactly match an existing
name in the SecUser.txt file.The User ID (login name) is case sensitive.
You can create a default user by entering “*” in the User ID column. If this
entry exists, then the system uses the Default Group, Default Units and
Allowed Groups for any user who accesses the system and is not specified in
the user ID list.
• Default Group - The Initial Group is the group that first displays when the
user logs into the MSC Enterprise Mvision system. The initial group also
controls the initial Navigation View that is selected. The system uses the first
Navigation View from the group, as listed in the active
GroupConfiguration.txt file, as the default view for login and when the
group is changed. The default databank is the first datasource listed in the
referenced Navigation View. If the default group is not a valid group, the
system uses the first valid group listed for the user ID.
• Default Unit Systems - The Initial Unit Systems sets the unit system for the
current databank. Each time the user accesses a databank, the system
attempts to set the default units. If this unit system is not available for a
databank then the first unit system in the databank units file <databank>.unt
is used. The specified unit system name must exactly match the unit system
name in the <databank>.unt file to take effect.
• Allowed Groups - The allowed groups specify all of the groups to which the
user has access. Because the groups control the Navigation Views and
databanks, these groups control which databanks and databank rows, via
category queries the user can access. This provides an effective method to
control databank access for different users.
Note: It is possible to change the group by changing databanks because the available
databank list is an aggregate of all of the databanks for all of the allowed
groups.
126
To add or modify user access or defaults, you must edit the UserList.txt file as follows:
1. Open the file <emv_root>/config/UserList.txt for editing.
2. Add or modify the User ID, Default Group, Default Unit System and the allowed
groups which this user is allowed to access. Allowed groups must include the
Default Group. All of the groups entered must be in the active
<emv_root>/config/GroupConfiguration.txt file to be valid groups. If not, an
error occurs when the user attempts to access the invalid group.
3. Close and save the UserList.txt file.
4. For the changes to take effect, it is recommended that the MSC Enterprise
Mvision server be stopped and restarted. You can also invoke changes to the user
access files using the Administrative Panel Interface, Chapter 6. This invokes
changes online and alerts the active clients. After active users logout and login
again, all changes are in effect.
<emv_root>/log/EmvLog.txt file. Look at the end of the file for the last “Starting
EMV...” line and verify no error messages exist.
Note: The MSC Enterprise Mvision system also provides you with the capability of
specifying the above mentioned user login information from another source
(instead of the default UserList.txt file). Refer to the section on Customizing
UserList.
Add/Modify a Group or Navigation View

To add or modify a group or Navigation View in MSC Enterprise Mvision, you must
modify the GroupConfiguration.txt file and the UserList.txt file to allow user access
to a newly created group. For changes to take effect you must restart or update the
MSC Enterprise Mvision servers.
To add a group, the group name must be a unique name consisting of at least one
alpha or numeric character. The group name cannot contain spaces. Each group must
contain at least one valid Navigation View which must contain a Databank Reference
(datasource) and at least one Criteria and Category. See the section Configuration Files
on page 133 for a complete description of the required file content and format.
To add or modify a Group or Navigation View, edit the GroupConfiguration.txt file as
follows:
1. Open the file <emv_root>/config/GroupConfiguration.txt file for editing.
2. To add a new group add the following lines to the file:
GROUP:"<Groupname>";
END_GROUP;
Add the required Navigation View within the new group.
CHAPTER 5 127
3. To add a new Navigation View to a new or existing group, add the data shown
below. These lines must be enclosed within the Group: and End_Group; tags to
which the view applies.
A Navigation View must be contained within a GROUP and END_GROUP statement.
Each Navigation View contains the format:
NAVIGATION_VIEW: "<Viewname>";
DATASOURCE: "<datasource name from databases.txt>";
NAVIGATION_TABLE: "the lowest level hierarchical relation name";
CRITERIA;
LABEL: "<Name of Criteria>";
EXPRESSION: "<Expression used to create query>";
OPERATOR: "<Operator used to create query";
VALUE: "<initial value of query>";
END_CRITERIA;
.... One or many Criteria can be specified
CATEGORY;
LABEL: "<Name of Category>";
COLUMN_HEADERS: "<List of databank expressions or attribute names
separated by commas>";
PROPERTY_VIEW: "<Relation name to perform query on>";
QUERY_STRING: "<Query to apply at all times while this category is
current>";
END_CATEGORY;
.... One or many Categories can be specified
END_NAVIGATION_VIEW;
Note: The positioning of the Navigation View in the group is important. The first
Navigation View in the group is always the default Navigation View when the
group is selected.
4. Close and save the file.
5. If a new group is added verify that the group has been assigned to the proper
users in the UserList.txt file. See Add/Modify a User on page 124.
Mvision servers be stopped and restarted. You can also invoke changes to the
user access and configuration file using the Administrative Panel Interface,
Chapter 6.
7. After the server has restarted, verify that no errors occurred when the server is
restarted by viewing the <emv_root>/log/EmvLog.txt file. Look at the end of the
file for the last “Starting EMV...” line and verify no error messages exist.
128
Add/Update Databank or Databank Support Files

The MSC Enterprise Mvision system can access and display data from any valid MSC
Enterprise Mvision databank supplied by MSC Enterprise Mvision or created by the
customer using MSC Enterprise Mvision Builder. In addition to adding new
databanks to the system, it may be required that existing databanks and/or databank
support files be modified or updated if the information in these files change.
To add a MSC Enterprise Mvision databank to the MSC Enterprise Mvision system:
1. Copy or convert <databank.des> and support files.
2. Create wrapper for disclaimer.
3. Modify <emv_root>/config/Databases.txt file.
4. Modify <emv_root>/config/GroupConfiguration.txt file.
Review Using MSC Enterprise Mvision Databanks on page 107 for detailed
procedures and other databank related requirements.
To update any databank file or support file that is already used in the MSC Enterprise
Mvision system, overwrite or edit the existing file contents with the new information.
Do not change the file location or file name. The changes take effect when the MSC
Enterprise Mvision servers are stopped and restarted (that is, the databank is reloaded
and auxiliary files are read) or if you update the databank using the Administrative
Panel Interface, Chapter 6.
To add a new databank perform the following steps:
1. Copy or link (UNIX/Linux only) the databank file <databank>.des, the
associated units file <databank>.unt, mapping file (if it exists),
<databank>.mvform and any supporting image and full-text files into the
<emv_databases_dir> directory. If a units file is not available, create an empty file
and name it <databank>.unt. Refer to Converting Databanks for Use with MSC
Enterprise Mvision on page 108.
2. Copy the disclaimer file to the <web_server_root>/docs/msc/emv/disclaimers
directory and create the required <databank>.shtml wrapper. See Creating
Databank Disclaimers on page 122 for details.
3. Add the databank name to the <emv_root>/config/Databases.txt file. Refer to
Converting Databanks for Use with MSC Enterprise Mvision on page 108.
CHAPTER 5 129
4. Create a Navigation View for the databank using one of the methods described
below and insert the Navigation View in one or more of the Groups defined in the
GroupConfiguration.txt file.
• Convert an existing MSC Mvision form.definitions or a <data

bank>.mvform file to a GroupConfiguration.txt file using the utility
program FormDef2GrpConfig. Refer to Creating GroupConfiguration.txt From
a Form File on page 113.
• Create a default Navigation View for a databank using the
AddDefaultDbNavView utility program. Refer to Creating Default
Navigation Views for MSC Enterprise Mvision on page 117.
• Create the Navigation View using a text editor. This requires knowledge of
the databank schema and contents.
Mvision servers be stopped and restarted. You can also invoke the changes to the
configuration settings using the Administrative Panel Interface, Chapter 6. This
invokes the changes online and alerts the active clients. After the active clients
logout and login again, all changes are in effect.
<emv_root>/log/EmvLog.txt file. For access to a databank, the user must have
access to the Group that contains a navigation view for the databank. The
UserList.txt file controls users access to groups. Refer to Add/Modify a User on
page 124.
The following is a detailed example of how to add a databank to the MSC Enterprise
Mvision system:
To add a new databank name analysis.des:
1. Copy the existing files analysis.des, analysis.unt and analysis.mapping into
2. Copy the disclaimer file analysis.dis into the <web_server_ root>

/docs/msc/emv/disclaimers directory. Create an analysis.shtml file in the same
directory by copying and modifying an existing .shtml file and changing the “#
include” line to “file=analysis.des”.
3. Open the <emv_root>/config/Databases.txt file and add the following line:
Analysis, analysis.des,8000
Note: Analysis is now recognized by MSC Enterprise Mvision as an alias to the

databank file <emv_databases_dir>analysis.des and this alias is used
throughout the system.
130
4. Open the <emv_root>/config/GroupConfiguration.txt file and insert the

following lines between any GROUP and END_GROUP statements:
NAVIGATION_VIEW: "Your New Analysis View";
DATASOURCE: "Analysis";
NAVIGATION_TABLE: "ENVIRONMENT";
CRITERIA;
LABEL: "Category";
EXPRESSION: "CATEGORY";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Type";
EXPRESSION: "TYPE";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CATEGORY;
LABEL: "Materials w/ FEA Ready Properties-Detail Listing";
COLUMN_HEADERS: "CATEGORY", "TYPE", "CNAME";
PROPERTY_VIEW : "FEA_PROPERTIES";
QUERY_STRING : "_FEA_PROPERTIES.row_id != 0";
END_CATEGORY;
5. Verify that a user has access to the group that contains the newly added
Navigation View. If not, edit the <emv_root>/config/UserList.txt file to allow
user access to the group.
6. Stop and restart the MSC Enterprise Mvision Servers or update the configuration
files using the Administrative Panel Interface, Chapter 6.
7. Verify that no errors occurred by viewing the <emv_root>/log/EmvLog.txt file.
8. Log on to MSC Enterprise Mvision as the user that has access to the group that
contains the newly added Navigation View.
9. Change to the group which contains the newly added Navigation View or select
the databank from the databank selection page. Verify that the databank and
view are accessible.
CHAPTER 5 131
To add or update a databank support file such as a .unt or .mapping file:

• Copy the modified file to the appropriate location within the MSC Enterprise
Mvision file structure and reload the associated databank by restarting the
MSC Enterprise Mvision servers or using the Administrative Panel Interface,
Chapter 6.
The revised support files are read when the databank is reloaded.
To update a template file or executable for an Export External Function:
• Copy the file to the <emv_root>/External_Function directory. The revised
file is read the next time the Export Function is executed.
132
Legend Display Customization

The content of the Legend entries associated with a Png image can be modified by the
user using functionality in the Data Display Settings. Previous versions of the
software limited the length of the legend entries 40 characters, often resulting in
truncation of information specified by the user. EMV 2008r1 introduces ‘floating
legends’ that automatically reposition beneath the Png image if the string length of the
legend entries becomes excessive.
‘Floating legends’ are enabled by adding the following line to the Emv.properties file in
the <emv_install_dir>/config directory:
legend_position = below
If this line is commented out or has no value, the original EMV legend positioning and
string length will apply.
The actual positioning of the legend box relative to the Png image and its appearance
is controlled by the Style sheet for the Power User and Advanced Interfaces, which are
located in the EMV web server installation directory: <webserver_context>/msc/emv
The classes that control the Legend formatting are as follows:
Element Definition
DIV.extraheight Controls the spacing between tables in the
Export.html page.
TABLE.legendbelow Formats the left margin, top margin,

background color, borders, position (float),
and display of the table legends in the
Export.html page.
TD.legendbelow Formats the font size, wrapping, and
padding of the legend entry when it is
positioned below the Png figure in the
Export.html page.
Image Size Customization

In version 2008r1, two properties were added to the FigureToPngServer.properties file
to control the size of the charts generated by the FigureToPng server:
• chartXsize - The size in pixels of the generated chart in the X axis
• chartYsize - The size in pixels of the generated chart in the Y axis
Both values default to 500 pixels, the current size.
CHAPTER 5 133
Configuration Files
The following section provides a detailed description of the format and syntax of the
configuration and user access files used in the MSC Enterprise Mvision system.
GroupConfiguration.txt
<emv_root>/config/GroupConfiguration.txt
The ‘users view’ of the databank, which refers to the content and layout of the
retrieved rows in both the flat and hierarchy views of the datalist, the category list,
navigation view, group list, and criteria queries, is controlled by the use of one or more
of the GroupConfiguration.txt, the SecQuery.xml, or EmvUserLoginDataAPI.cpp files.
This section defines use of the file, GroupConfiguration.txt. See “Security Files” on
page 144.
The Group Configuration.txt file defines the “users view” of a databank and allows
data to be grouped into logical units. Each grouping, called a Group, contains one or
more Navigation Views. The Navigation View contains the information that describes
how and what data within a databank is to be displayed. This information includes
Criteria conditions, attribute based queries, used to search the databank’s data and
Categories which define the content and presentation of the data in the Material List
page.
A Group provides you the ability to control access to the databank information, by
creating Navigation Views that contain a particular databank or data sets and
including them in a specific Group. These groups can then be specified in the
UserList.txt file, which controls the user’s access to the predefined databanks or data
sets.
The GroupConfiguration.txt file contains one or many groups, each group containing
one or many views of the available data. Each view is made up of: a data source (for
example, mil5.des) a reference to a specific databank, a navigation table such (for
example, ENVIRONMENT) that defines the lowest level hierarchy table; list of
Criteria definitions that provide pre-defined queries and a list of Categories that
define the Material List’s data content and display format.
The GroupConfiguration.txt file can contain comments. To add a comment to this file,
use the C/C++ notation of /* some comment here */ where the ‘/*’ and ‘*/’ start and
end the comment in the file. The lines in this file can have a maximum line length
100000 characters. Its also possible to split a line into two lines using a carriage return
as long as the carriage return is not between a quoted string.
Note: The current category query is always in effect when the user has selected a
Navigation View (that is, all subsequent queries are added to this base query).
This query restricts the information (which rows in the databank) to which the
user has access.
134
The user’s default (initial) group is specified in the <emv_root>/config/UserList.txt

file. The default (initial) Navigation View listed is the first Navigation View in the
group as it appears in the GroupConfiguration.txt file. The default (initial) category
is the first category listed within the Navigation View.
CHAPTER 5 135
The following is an example of the content, format and syntax of a typical

GroupConfiguration.txt file:
GROUP: "Design";
NAVIGATION_VIEW : "SAMPLE DATA --- DEMONSTRATION Fatigue Data from Various

Sources";
DATASOURCE : "fatigue";
NAVIGATION_TABLE : "TEST_CONDS";
CRITERIA;
LABEL: "Material Name";
EXPRESSION: "NAME";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "US Designation";
EXPRESSION: "US_SPEC";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "UK Designation";
EXPRESSION: "UK_SPEC";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Physical Form";
EXPRESSION: "SOURCE";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Heat Treatment";
EXPRESSION: "HEAT_TREAT";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
136
CRITERIA;
LABEL: "Test Temperature";
EXPRESSION: "TEST_TEMP";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Orientation";
EXPRESSION: "ORIENTATION";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Microstructure";
EXPRESSION: "MICROSTRUCT";
OPERATOR: "Like";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Min. Modulus";
EXPRESSION: "E";
OPERATOR: ">=";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Min. Yield Strength";
EXPRESSION: "SY_MONO";
OPERATOR: ">=";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Min. Cyclic Yield Strength";
EXPRESSION: "SY_CYCL";
OPERATOR: ">=";
VALUE: "";
END_CRITERIA;
CRITERIA;
LABEL: "Min. Ultimate Strength";
EXPRESSION: "SU";
OPERATOR: ">=";
VALUE: "";
END_CRITERIA;
CHAPTER 5 137
CATEGORY;
LABEL: "List ALL Materials";
COLUMN_HEADERS: "NAME", "US_SPEC", "UK_SPEC", "SOURCE",
"HEAT_TREAT", "TEST_TEMP", "ORIENTATION", "MICROSTRUCT";
PROPERTY_VIEW : "TEST_CONDS";
QUERY_STRING : "true";
END_CATEGORY;
CATEGORY;
LABEL: "Property Data";
"HEAT_TREAT", "TEST_TEMP", "ORIENTATION", "MICROSTRUCT";
PROPERTY_VIEW : "PROPERTY";
QUERY_STRING : "_PROPERTY.row_id != 0";
END_CATEGORY;
CATEGORY;
LABEL: "Stress vs Strain Curves";
"HEAT_TREAT", "TEST_TEMP", "ORIENTATION", "MICROSTRUCT", "SIGvsEPS";
PROPERTY_VIEW : "SIGvsEPS";
QUERY_STRING : "(SIGvsEPS EX) and (_SIGvsEPS.row_id != 0)";
END_CATEGORY;
CATEGORY;
LABEL: "Strain Amp vs Life Curves";
"HEAT_TREAT", "TEST_TEMP", "ORIENTATION", "MICROSTRUCT", "EPSvsLIFE";
PROPERTY_VIEW : "EPSvsLIFE";
QUERY_STRING : "(EPSvsLIFE EX) and (_EPSvsLIFE.row_id !=
0)";
END_CATEGORY;
CATEGORY;
LABEL: "Max Stress vs Life Curves";
"HEAT_TREAT", "TEST_TEMP", "ORIENTATION", "MICROSTRUCT", "SIGEPSvsLIFE";
PROPERTY_VIEW : "SIGEPSvsLIFE";
QUERY_STRING : "(SIGEPSvsLIFE EX) and (_SIGEPSvsLIFE.row_id
!= 0)";
END_CATEGORY;
138
CATEGORY;
LABEL: "Show ALL Curves";
COLUMN_HEADERS: "NAME", "SIGvsEPS", "EPSvsLIFE", "SIGEPSvs-
LIFE";
PROPERTY_VIEW : "SIGvsEPS";
QUERY_STRING : "(SIGvsEPS EX) and (_SIGvsEPS.row_id != 0)";
END_CATEGORY;
The following table describes the labels (tags) and statements used in the
GroupConfiguration.txt file. In general, the file syntax requires all values to be within
double quotes and that each line is terminated with a semicolon.
Tags and Statements in GroupConfiguration.txt
Tag: Value: Example:

GROUP Double-quoted string of characters “DESIGN”
defining the name of the group. The
group name must be a unique name
of at least one alpha or numeric
character. The group name cannot
contain spaces.
NAVIGATION_VIEW Double-quoted string of characters “Sample Data ---
defining the name of the Navigation Demonstration fatigue
View. The Navigation View name data from various
can be any combination of alpha or sources””
numeric characters and must be
unique within a group. The
positioning of the navigation view
within the group is important. The
first Navigation View listed is
always the default Navigation View
when the group is selected.
DATASOURCE Double-quoted string of characters
mapping to a data source name in “FATIGUE”
the Databases.txt file. This name
must match the name listed in the
Databases.txt file exactly.
NAVIGATION_TABLE Data Source table name that is used “TEST_CONDS”

as the last hierarchy (pedigree)
table, the lowest level hierarchy
table.
CHAPTER 5 139
Tags and Statements in GroupConfiguration.txt (Continued)

CRITERIA Signifies the beginning of a Criteria
definition. At least one valid criteria
must be included or the view is
invalid.
LABEL Label (name) of Criteria that “MATERIAL NAME”
displays in the Criteria Selection
List.
EXPRESSION Expression combined with operator "NAME"
and values to form a query
condition. This is typically an
attribute name, but can be any valid
expression.
OPERATOR Operator combined with "LIKE"
Expression and Values to form a
query condition. This can be any
valid MSC Enterprise Mvision
Operator that is compatible with the
expression “Type” (i.e. string, real,
integer, figure, etc.).
VALUE User-specified value to be “”
combined with Expression and
Operator to form a query condition.
This value is typically “Null” to
allow the user to specify the value in
the interface.
END_CRITERIA Terminator for CRITERIA.
CATEGORY Signifies the beginning of a
Category definition. At least one
valid category must be included or
the view is invalid.
LABEL Label (name) of Category that "PROPERTY DATA"
displays in the Category Selection
List.
140
Tags and Statements in GroupConfiguration.txt (Continued)

COLUMN_HEADERS Datasource expressions or attribute “NAME”, “US_SPEC”,
names to use as column headers “UK_SPEC”, and so on
and display values in the Material
List. These values can be any
attribute name or computed
attribute that is valid for the subject
databank. Multiple values can be
listed as comma separated quoted
strings. These are the default
column headers that are displayed
when the category is selected.
PROPERTY_VIEW The default data relation (table) to "PROPERTY”
display in the Export page Selection
List.
QUERY_STRING Any valid MVISION query for the “_PROPERTY.ROW_ID
subject databank which determines !=0”
the information available to the
current user and the content of the
material list. The query must be
contained within double quotes.
END_CATEGORY Terminator for CATEGORY.
END_NAVIGATION_V Terminator for NAVIGATION_VIEW
IEW
END_GROUP Terminator for GROUP
Note: For more information on MSC Enterprise Mvision query language and syntax,
refer to the MSC Enterprise Mvision Builder and Evaluator User’s Guide and
Reference, or the help information provided in MSC Enterprise Mvision
“Advanced Search” page.
CHAPTER 5 141
Databases.txt
<emv_root>/config/Databases.txt
The Databases.txt file contains the data source file mapping (cross reference) to the
MSC Enterprise Mvision databanks. This file contains a list of rows for data source
mappings. Each row contains a data source label (name) and an MSC Enterprise
Mvision databank name. The data source label can be any combination of
alphanumeric characters. The data source label can not contain spaces. The databank
name must be relative to the <emv_databases_dir> directory and must exactly match
the databank filename. The third entry is an optional databank specific cache size
specified in kilobytes.
The file entries are order dependent and must be comma delimited as shown in the
following example:
Super, SuperDb.des, 1000
User, UserDb.des, 50000
XYZ, Xyz.des
Note that the Data Source XYZ does not have a cache size specified. For this databank
a default of 8000k is used. If no cache size is specified, or if the value is less than 1 or
greater than 100,000, the default of 8000 is automatically used. Some consideration
should be given to specifying the cache size. This effects the system performance. If
the cache size is too small, the system performance decreases due to paging when
handling large amounts of data. If the cache size is too large, available memory is
wasted. Typically 50% of the databank size is adequate, but you may want to adjust
this value to determine optimum performance.
The Databases.txt file can contain comments. To add a comment to this file, add a ‘#’
to the beginning of the line you want ignored by the system. This must be the first
character in the line. The lines in this file can have a maximum line length 2560
characters. Do not split a line into two lines using a carriage return.
142
The following table is an example of column entries for the Databases.txt file.
Column Entries for Databases.txt
Databank MSC Enterprise Optional databank

Data source label:
Mvision: cache size in kilobytes:
Super SuperDb.des 1000
User UserDb.des 50000
XYZ Xyz.des
UserList File
<emv_root>/config/UserList.txt
The UserList.txt file contains the user names and default parameters for users who
are allowed to access MSC Enterprise Mvision. The default (initial) group, the default
(initial) unit systems, and the groups that are available to a specific user are specified
in this file. Only those groups that are listed in the “Allowed Groups” are available to
the user and are displayed in the Group Selection list.
For each user, the databanks that are available to that specific user is a collection of all
of the databanks specified in the navigation views for the groups to which the user has
access. The “allowed groups” provide a method to limit user access to specific data by
creating groups that contain only a specific set of databanks with predefined views of
the data. Any group not listed in the UserList.txt file is not accessible by any user.
The group names must exactly match the group names as stated in the
GroupConfiguration.txt file.
The following table is an example of column entries for the UserList.txt file.
Column Entries for UserList.txt
User ID: Default: Default units: Allowed:

SuperUserClarkKent SuperUser US-Customary User, SuperUser
NormalUserLoisLane User SI-Customary User
As shown in the table above:

• First item is the user name (as defined in the SecUser.txt file),
• Second item is the default group.
CHAPTER 5 143
• Third item is the default units system (this should match a valid units system
name as defined in the primary <databank>.unt file to which the user has
access).
• Fourth and subsequent items are a comma-delimited listing of all groups to
which the user has access.
You can create a default user by entering “*” in the user ID column. If this entry exists,
then the system uses the default group, default units, and allowed groups for any user
who accesses the system and is not specified in the listed user ID.
Note: The “Default Group” must also be listed in the “Allowed Groups”.
The file entries are order dependent and must be comma delimited as shown in the
following example:
SuperUserClarkKent, SuperUser, US-Customary, User, SuperUser
NormalUserLoisLane, User, SI-Customary, User
In the example above all the views in groups User and SuperUser are available to
SuperUserClarkKent. But the user NormalUserLoisLane does not have access to the
SuperUser group. Also in the above example the users have different “Default
Groups” which is the second parameter. If the default group is not a valid group the
system uses the first valid group that is listed for “Allowed Groups”.
The third parameter sets the user’s “Default” units system. Each time a databank is
accessed the system attempts to set the default units file system. The “Default Units”
entry must match the DB label in a databank’s units file. Otherwise, the databank
default, the first unit system listed in the <databank>.unt file establishes the active
unit system.
The UserList.txt file can contain comments. To add a comment to this file, add a ‘#’ to
the beginning of the line you want ignored by the system. This must be the first
character in the line. The lines in this file can have a maximum line length of 2560
characters.
To split lines across two or more lines, use a back slash character (/) at the end of the
line, as shown below.
SuperUserClarkKent, SuperUser, US-Customary, User, \
SuperUser
NormalUserLoisLane, User, SI-Customary, User
Refer to Add/Modify a User on page 124 for specific information on the use of this file.
(instead of the default UserList.txt file). Refer to the section on Customizing
UserList.
144
HTML Template Files

<emv_root>/html/<files>
The HTML template files in the <emv_root>/html directory contains the information
to format and display MSC Enterprise Mvision data in HTML pages. The collection of
these pages compose the user interface.
An HTML template file can contain HTML, JavaScript, and MSC Enterprise Mvision
tags. The JavaScript is used to connect the HTML buttons, actions, and events so that
the correct MSC Enterprise Mvision tag value can be set and then sent to the Web
server for processing by the MSC Enterprise Mvision server. The MSC Enterprise
Mvision tags are used to extract databank information in predefined HTML formats.
You can think of an MSC Enterprise Mvision tag as being like a variable in a
programming language where it contains a value. That value is displayed using
HTML in a browser. Refer to the Using MSC MVISION Materials Evaluator for a
complete discussion of HTML templates and their function.
Subdirectories are used to hold logical groupings of HTML pages. It is important to
note that the page references used in the HTML pages are relative to
<emv_root>/html. To access an HTML template under the subdirectory simple, the
page reference you would use is simple/<page>. You can use an HTMLBASE tag to
specify a subdirectory that all page references have added to their path before the page
is looked up.
Security Files
<emv_root>/security/SecUser.txt
The SecUser.txt file contains the user names and password that the standard MSC
Enterprise Mvision security system uses to validate user authorization for access to
the system. The file is a listing of rows composed of three comma-delimited fields:
• User name
• Password
• Required field, which is always 0
The MSC Enterprise Mvision system reads this file each time a user attempts to
connect to the MSC Enterprise Mvision server to validate the user ID and password
before allowing the user access to the data. If the validation fails, an error message is
returned. As installed from the MSC Enterprise Mvision CD-ROM, the standard MSC
Enterprise Mvision security is in effect. The installed software contains a default user
of “guest” with a password of “emv” as the only entry in the file
<emv_root>/security/SecUser.txt. You should remove this user to prevent
unauthorized access to your MSC Enterprise Mvision system.
CHAPTER 5 145
You can also create your own security API using the files provided in the
<emv_root>/src/Security_api directory. For the Windows XP platform, use the
skeleton project. Modify the .dsp (Visual Studio project) file, and the .cpp (C++ Source
Files) and header files to create and compile your site specific user validation system.
For the UNIX/Linux platform, modify the makefile, the C++ source files and header
files to compile your custom API program. When you have created your custom API,
replace the MSC Enterprise Mvision supplied API executable in the
<emv_root>/bin/.bin directory and reinitiate the system.
The SecUser.txt file entries are order dependent and must be comma delimited as
shown in the following example:
SuperUserClarkKent, HI, 0
NormalUserLoisLane, Bye, 0
The following table is an example of column entries for the SecUser.txt file.
Column Entries for SecUser.txt
User ID: Password: Required parameter:
SuperUserClarkKent HI 0
NormalUserLoisLane Bye 0
As shown in the table above:

• First item is the user name, which can be any combination or number of
alpha/numeric characters, but cannot contain spaces.
• Second item is the user’s password, which can be any combination or number of
alpha/numeric characters, but cannot contain spaces.
• Third item is a required parameter value and must be zero.
Note: The user name and password only applies to the MSC Enterprise Mvision
system and is not related to, or extracted from any login name or password for
shells or other applications.
The SecUser.txt file cannot contain comments. The lines in this file can have a
maximum line length 2560 characters. Do not split a line into two lines using a carriage
return. Both user name and password are case sensitive.
(instead of the default SecUser.txt file). Refer to the section on Customizing
SecUser.
146
<emv_root>/security/SecQuery.xml
The SecQuery.xml file augments the capability of the UserList.txt and
GroupConfiguration.txt files to filter the data that the authorized user of a databank
can view. As such, it can also be used to reduce the size and complexity of the
GroupConfiguration.txt file, which tends to grow in direct proportion to a
company’s security requirements. The functionality implemented in SecQuery.xml,
can be replicated and automated using the DatabaseQueryFilter() method in the
EmvUserLoginDataAPI. An example project can be found in the directory
<emv_root>/src/EmvUserLoginDataAPI, which can be modified, compiled, and used in
place of the library distributed with MSC Enterprise Mvision. See
“EmvUserLoginDataAPI.cpp” on page 152.
Since the SecQuery.xml file is XML-encoded, the first section of this file is devoted to
schema definition. The section that follows may be modified to meet security
requirements. In this file:
• the ‘user name’ refers to the User ID’s specified in the UserList.txt file
• the ‘database name’ refers to the name used as the DATASOURCE value in the
GroupConfiguration.txt file, which is cross-referenced to the binary
Mvision databank name in the Databases.txt file
• the ‘query’ is the value inserted between the ‘database’ tags.
For each ‘user’, only those databases listed in the SecQuery.xml file are filtered. The
user is denied or allowed access to all unlisted databases, supplementing the
conditions set by the UserList.txt and the GroupConfiguration.txt files. Each query
is valid for the duration of a session, unless the server is reset, at which time all user
sessions are terminated. In the following example, the user with User ID, guest, is
limited to viewing Chapter 2 of the MSC Mvision Demo Metals databank, Aluminum
Alloy LM25TB in the MSC Mvision Fatigue Databank, Chapter 7 of MSC Mvision
Mil-HDBK 5 Databank, and Graphite fiber in the MSC Mvision Fiber Databank.
<SecurityQuery>
<user name = 'guest'>
<database name = 'demo_metals'>chapter='2'</database>
<database name = 'fatigue'>name='AL ALLOY LM25TB'</database>
<database name = 'mil5_new'>chapter='7'</database>
<database name = 'fiber'>cname='GRAPHITE'</database>
</user>
</SecurityQuery>
The dbRestricted value specifies the default query behavior. If dbRestricted =
"false" access for any installed database which is missing from the Database list is
allowed, subject to the default configuration. If dbRestricted = "true", access for any
installed database which is missing from the listed databases is denied.
CHAPTER 5 147
These queries are implemented when the file is saved and the EmvServer is restarted
or updated via the Admin Panel. For use of the Admin Panel, see
148
Customizing User Login Environment

The MSC Enterprise Mvision system provides you with the capability of specifying
user login related information (security information, default user parameters, and so
on) from various data sources. To take advantage of these features, you must
implement the interfaces documented in the following sections.
Customizing UserList
The MSC Enterprise Mvision system has the capability of obtaining user login-related
information (User ID, Default Group, Default Units, Allowed Groups) from various
sources. MSC Enterprise Mvision, when installed with its default configuration,
obtains the user login related information from the flat text file UserList.txt. In MSC
Enterprise Mvision, the capability of obtaining this information from a user-defined
source has been provided. This capability is implemented through the use of a
DLL/Shared Library (EmvUserLoginData.dll / EmvUserLoginData.so).
An example project can be found in the directory
<emv_root>/src/EmvUserLoginDataAPI, which can be modified, compiled, and used in
place of the library distributed with MSC Enterprise Mvision.
To take advantage of this new capability, the MSC Enterprise Mvision system
administrator can implement the above-mentioned DLL/Shared Library with the
interfaces described below and then replace the old library in <emv_root>/bin (on
Windows platforms) or <emv_root>/lib (on UNIX platforms) with the new one.
CHAPTER 5 149
Interface to be implemented in EmvUserLoginData.dll

IUserLoginData.h
.
.
.
class IUserLoginData {
public:
///////////////////////////////////////////////////////////////////////////////
// This method is intended for the purpose of establishing a connection to
// a user defined data source, initializing any user data, etc.
//
// int initUserLoginData (const void* handle)
//
// Input:const void*handle-For future use
//
// Return:intstatus- 0 = Success
// 1 = Failure
///////////////////////////////////////////////////////////////////////////////
virtual int initUserLoginData (const void* handle) = 0;
///////////////////////////////////////////////////////////////////////////////
// This method is intended for the purpose of re-establishing a connection to
// a user defined data source, initializing any user data, etc. This is typically
// called when the administrator updates the Group Configuration information
// from the Admin.jsp URL.
//
// int reInitUserLoginData (const void* handle)
//
//
// Return:intstatus-0 = Success
// 1 = Failure
///////////////////////////////////////////////////////////////////////////////
virtual int reInitUserLoginData (const void* handle) = 0;
///////////////////////////////////////////////////////////////////////////////
// This function retrieves user login information for a given user. Its purpose
// is to retrieve the users’ ID, Default Group, Default Units, and all Groups the
// user belongs to from a user defined data source.
// The function should allocate the required memory for the output strings, and
// the caller will free the allocated memory through the use of freeUserLoginData().
// Therefore, it is important that the proper combination of allocation and
// de-allocation methods are implemented.
// i.e.
// If 'malloc' is used, then use 'free' in 'freeUserLoginData()'
// If 'new' is used, then use 'delete' in 'freeUserLoginData()'
//
//
150
// int getUserLoginData (const void*handle,

// const char*user_name,
// char** user_id,
// char** default_group,
// char** default_units,
// char** allowed_groups)
//
//
// Input:const void*handle - For future use
// const char*user_name- Retrieve login information for specified
// user
//
// Output:char** user_id -Given users’ User ID
// char** default_group-Given users’ Default Group
// char** default_units-Given users’ Default Units
// char** allowed_groups-All groups the given user belongs to.
// This should be a list of comma separated
// Group names.
//
// Return:intstatus - 0 = Success
// 1 = Failure
///////////////////////////////////////////////////////////////////////////////
virtual int getUserLoginData (const void* handle, const char* user_name,
char** user_id, char** default_group,
char** default_units,
char** allowed_groups) = 0;
///////////////////////////////////////////////////////////////////////////////
// This function de-allocates the user login data strings that are passed in.
//
// If 'malloc' is used in 'getUserLoginData', then use 'free'
// If 'new' is used in 'getUserLoginData', then use 'delete'
//
// void freeUserLoginData (constvoid*handle,
// char*user_id,
// char*default_group,
// char*default_units,
// char*allowed_groups)
//
//
// char* user_id -Users’ User ID
// char* default_group-Users’ Default Group
// char* default_units-Users’ Default Units
// char* allowed_groups-List of Groups the user belongs to
//
// Output:None
//
// Return:None
//
///////////////////////////////////////////////////////////////////////////////
virtual void freeUserLoginData (const void* handle, char* user_id,
char* default_group, char* default_units,
char* allowed_groups) = 0;
};
.
.
.
CHAPTER 5 151
Example of Interface Implementation

EmvUserLoginDataAPI.h
#ifndef EMV_USERLOGINDATA_API_H
#define EMV_USERLOGINDATA_API_H
#include "IUserLoginData.h"
class EmvUserLoginDataAPI : public IUserLoginData {

public:
EmvUserLoginDataAPI ();
public: // Factory to create this type of API

static IUserLoginData *create () {
return new EmvUserLoginDataAPI ();
}
public:
// IUserLoginData Interface
int initUserLoginData (const void* handle);
int reInitUserLoginData (const void* handle);
int getUserLoginData (const void* handle, const char* user_name,

char** user_id, char** default_group,
char** default_units, char** allowed_groups);
void freeUserLoginData (const void* handle, char* user_id,

char* default_group, char* default_units,
char* allowed_groups);
};
#endif // EMV_USERLOGINDATA_API_H
152
EmvUserLoginDataAPI.cpp
.
EmvUserLoginDataAPI::EmvUserLoginDataAPI ()
{
}
int EmvUserLoginDataAPI::initUserLoginData (const void* handle)

{
// Always return 'success' for now until implemented
return 0;
}
int EmvUserLoginDataAPI::reInitUserLoginData (const void* handle)

{
// Always return 'success' for now until implemented
return 0;
}
int EmvUserLoginDataAPI::getUserLoginData (const void* handle,

const char* user_name,
char** user_id,
char** default_group,
char** default_units,
char** allowed_groups)
{
// Implement your custom User Login Data retrieval functionality
// here, instead of the following
*user_id = *default_group = *default_units = *allowed_groups = NULL;
if (strcmp(user_name, "guest") == 0)
{
// Memory allocated for the following strings will be
// de-allocated using a subsequent call to 'freeUserLoginData'
*user_id= strdup ("guest");
*default_group= strdup ("Design");
*default_units= strdup ("AsStored");
*allowed_groups= strdup ("Design,Aero,Auto");
}
return 0;
}
void EmvUserLoginDataAPI::freeUserLoginData (const void *handle,

char* user_id,
char* default_group,
char* default_units,
char* allowed_groups)
{
// Implement your custom memory de-allocation method here:
// If 'malloc' is used in 'getUserLoginData', then use 'free'
// If 'new' is used in 'getUserLoginData', then use 'delete'
if (user_id != NULL)
free (user_id);
if (default_group != NULL)
free (default_group);
if (default_units != NULL)
free (default_units);
if (allowed_groups != NULL)
free (allowed_groups);
}
CHAPTER 5 153
Customizing SecUser
The MSC Enterprise Mvision system has the capability of validating user login
information (User ID, Password, DataBank Authorization, and so on) through an external
source. MSC Enterprise Mvision, when installed with its default configuration,
validates the user login information using the flat text file SecUser.txt. The validation
of user login information is implemented through the use of a DLL/Shared Library
(SecurityAPI.dll/SecurityAPI.so).
An example project can be found in the directory <emv_root>/src/ Security_api,
which can be modified, compiled and used in place of the library distributed with
MSC Enterprise Mvision.
In order to take advantage of this capability, the MSC Enterprise Mvision system
administrator can implement the above mentioned DLL/Shared Library with the
interfaces described below and then replace the old library in <emv_root>/bin (on
Windows platforms) or <emv_root>/lib (on UNIX platforms) with the new one.
154
Interface to be implemented in SecurityAPI.dll

ISecurity.h
#ifndef ISECURITY_H
#define ISECURITY_H
////////////////////////////
// Message display interface
////////////////////////////
class ISecurityMsg {
public:
virtual void secDisplayInfoMsg( const char *msg ) = 0;
virtual void secDisplayWarningMsg( const char *msg ) = 0;
virtual void secDisplayErrorMsg( const char *msg ) = 0;
};
////////////////////////////////
// Customized Security interface
////////////////////////////////
class ISecurity {
public:
#if defined(SUNS) || defined(RS6K)
///////////////////////////////////////////////////////////////////////////////
// This method determines whether a user is authorized to access a
// given database.
//
// int isUserAuthforDb (const char *username, const char *db_name)
//
// Input:const char*username-User Name
// const char*db_name-Database Name
//
// Return:intstatus - 1 = Success (user is authorized)
// 0 = Failure (user is not authorized)
///////////////////////////////////////////////////////////////////////////////
virtual int isUserAuthforDb( const char *username, const char *db_name ) = 0;
///////////////////////////////////////////////////////////////////////////////
// This method determines whether a user is authorized to access the system
//
// int isUserPasswordValid (const char *username, const char *password, const int
client_type)
//
// const char*password-User Password
// const intclient_type-Type of Client accessing the system
// 0 = WEB Client
// 1 = Integrated Client
//
// Return:intstatus - 1 = Success (user is authorized)
// 0 = Failure (user is not authorized)
///////////////////////////////////////////////////////////////////////////////
virtual int isUserPasswordValid( const char *username, const char *password, const
int client_type ) = 0;
CHAPTER 5 155
ISecurity.h (con’t.)
#else
///////////////////////////////////////////////////////////////////////////////
// This method determines whether a user is authorized to access a
// given database.
//
// int isUserAuthforDb (const char *username, const char *db_name)
//
// const char*db_name-Database Name
//
// Return:boolstatus - true = Success (user is authorized)
// false = Failure (user is not authorized)
///////////////////////////////////////////////////////////////////////////////
virtual bool isUserAuthforDb( const char *username, const char *db_name ) = 0;
///////////////////////////////////////////////////////////////////////////////
// This method determines whether a user is authorized to access the system
//
// int isUserPasswordValid (const char *username, const char *password, const int
client_type)
//
// const char*password-User Password
// const intclient_type-Type of Client accessing the system
// 0 = WEB Client
// 1 = Integrated Client
//
// Return:boolstatus - true = Success (user is authorized)
// false = Failure (user is not authorized)
///////////////////////////////////////////////////////////////////////////////
virtual bool isUserPasswordValid( const char *username, const char *password, const
int client_type ) = 0;
#endif
};
#endif // ISECURITY_H
156
Example of Interface Implementation

EmvSecurityAPI.h
#ifndef EMV_SECURITY_API_H
#define EMV_SECURITY_API_H
#include "ISecurity.h"
// **********
class EmvSecurityAPI : public ISecurity {

public:
EmvSecurityAPI( const char *emv_security_dir, ISecurityMsg *isecurity_msg, int argc, char **argv );
public: // Factory to create this type of api

static ISecurity *create( const char *emv_security_dir, ISecurityMsg *isecurity_msg, int argc, char
**argv ) {
return new EmvSecurityAPI( emv_security_dir, isecurity_msg, argc, argv );
}
public:
// ISecurity Interface
int isUserAuthforDb( const char *username, const char *db_name );
int isUserPasswordValid( const char *username, const char *password, const int client_type );
#else
bool isUserAuthforDb( const char *username, const char *db_name );
bool isUserPasswordValid( const char *username, const char *password, const int client_type );
#endif
private:
// Interface implemented in EMV to display message to log file/GUI

ISecurityMsg *m_isecurity_msg;
// Emv installed directory eg "c:/emv/v1_0/security" or some other directory

const char *m_emv_security_dir;
};
#endif // EMV_SECURITY_API_H
CHAPTER 5 157
EmvSecurityAPI.cpp
include "StdAfx.h"
#if defined(WIN32) || defined(LINUX)
#include <string.h>
#else
#include <strings.h>
#endif
#include "EmvSecurityAPI.h"
// **********
ISecurity *CreateEmvSecurityAPI( const char *emv_security_dir, ISecurityMsg

*isecurity_msg, int argc, char **argv )
{
return new EmvSecurityAPI( emv_security_dir, isecurity_msg, argc, argv );
}
// **********
EmvSecurityAPI::EmvSecurityAPI( const char *emv_security_dir, ISecurityMsg

*isecurity_msg, int argc, char **argv )
{
// Store the passed in parms
m_emv_security_dir = strdup( emv_security_dir );
m_isecurity_msg = isecurity_msg;
}
// **********

int EmvSecurityAPI::isUserAuthforDb( const char *username, const char *db_name )
{
// Always return true for now until implemented
return 1;
}
#else
bool EmvSecurityAPI::isUserAuthforDb( const char *username, const char *db_name )
{
return true;
}
#endif
// **********
int EmvSecurityAPI::isUserPasswordValid( const char *username, const char *password,
const int client_type )
{
return 1;
}
#else
bool EmvSecurityAPI::isUserPasswordValid( const char *username, const char *password,
const int client_type )
{
return true;
}
#endif
158
URL Utilities
To assist in monitoring the status of the MSC Enterprise Mvision server and to
diagnose or trace system errors, the MSC Enterprise Mvision system provides URL
utilities.
Version and Log URLs

There are two URL utilities included with the MSC Enterprise Mvision system.
The first of these utilities checks the version of the MSC Enterprise Mvision system
and the second displays the MSC Enterprise Mvision server log files in a web browser.
The <hostname> specified in the following URL is the host machine where MSC
Enterprise Mvision is running.
To use the EMV Version utility, enter the following URL in your browser:
http://<hostname>/msc/emv/EmvVersion.html
This displays the build number of the system and system modification times for MSC
Enterprise Mvision related files, similar to the page shown below:
System Build Number and Modification Times.
To use the EMVLog utility, enter the following URL in your browser:
http://<hostname>/msc/emv/EmvLog.html
EmvLog.html displays an HTML page containing two frames. The top frame contains
a row-count selector and the bottom frame displays the last “X” number of lines in the
<emv_root>/log/EmvLog.txt file similar to the page shown below. The row-count
selector redisplays the bottom frame’s contents when the button to display the
contents (Show Log) is clicked. The indicated count is used in the bottom frame for the
row count.
CHAPTER 5 159
EMVLog HTML File

160
Implementing Export Functions for MSC Enterprise

Mvision
Customizing Export Using Perl
Overview
This section describes how to customize the export for MSC Enterprise Mvision using
Perl programming language. Perl customization and execution is MSC Enterprise
Mvision requires Perl Version 5.004 or higher.
Customizing an export using Perl involves the following five steps:
1. Define customizations in the schema.odl file
2. Generate the Perl code required for customizations
3. Write customized functions in Perl
4. Test the Perl functions
5. Use Customizations in MSC Enterprise Mvision
Each of these steps is described in this section as follows:
Step 1: Define Customizations in the schema.odl File

MSC Enterprise Mvision customizations are defined in the schema.odl located in the
<emv_root>/external_functions directory. The schema.odl file defines the export
view structures and action methods. It also defines the view mappings available for
each database entity (table).
A view structure is defined by a name, a set of attributes, and a set of actions.
view view_name;
{
<attribute_1_name> : attribute_1_type;
<attribute_2_name> : attribute_2_type;
action action_1_name() perl;

action action_2_name() perl;
};
CHAPTER 5 161
The following is an example for defining a view “Iso” with three attributes and two
actions:
view Iso
{
e: double;
g: double;
nu:double;
action writeMat1() perl;

action writeFile() perl;
};
The attribute types currently supported are “string”, “integer”, and “double”.
The view declaration defines a structure in a schema named “Util”. This is significant
because it affects where the Perl code for the ISO view is generated (See Step 7 in this
section).
The view mappings available for a database entity are defined as follows:
extension schema_name::entity_name
{
ViewMapping view_name() perl;
};
The following is an example for defining a view mapping from mil17a to the Iso view:
extension mil17a::ENVIRONMENT
{
ViewMapping Iso() perl;
};
Step 2: Generate the Perl Code

After the customization has been defined in the schema.odl file, the Perl code required
to integrate the user’s customizations into the MSC Enterprise Mvision system must
be generated. The required Perl code is generated using the executable IdcGenPerl
located in the directory <emv_root>/bin/.bin. The usage of IdcGenPerl is:
IdcGenPerl <emv_root> <emv_databases_directory>
<emv_external_functions_directory> <emv_config_directory>
For example, if MSC Enterprise Mvision is installed in c:/emv/2008r1 with the

databases, external functions and configuration directories as in the installed locations
then the command would be:
IdcGenPerl “c:/emv/2008r1” “c:/emv/2008r1/databases”
“c:/emv/2008r1/external_functions” “c:/emv/2008r1/config”
162
The IdcGenPerl executable generates Perl code, then tests the Perl customization
environment by running tests to validate that both Perl is available and that the Perl
code was generated properly. The IdcGenPerl program utilizes the schema.odl file in
<emv_root>/external_functions and the list of databases in the
<emv_root>/config/Databases.txt file.
For each view structure defined and database entity extension in the schema.odl file,
a Perl package is generated in the file
<emv_root>/external_functions/idc_perl/IDC/<schema_name>/<struct_name>.pm.
The name of the package is: IDC::<schema_name>::<struct_name>.

The functions generated in the package are:
• new() - returns a reference to an object in the package
• test() - validates the code generated in the package
• testMethods() - validates the customized code provided by user (See Step 3
in this section)
• testInit() - initializes value of data members to fixed values
• AUTOLOAD() - automatically provides data member access and
modification methods()
• newFromXmlFile(), readXml(), writeXmlFile(), writeXml() - are used to
communicate data between Perl and XML files.
The new() function returns a reference to an object with data members initialized
according to the following table.
Data Member Initialization
Attribute type: Perl type: Initial value:

String String “”
Integer Integer number 0
Double Double-precision 0.0
number
EngValue Reference to an new IDC_CORE::EngValue
IDC_CORE::EngValue
object
MimeFile Reference to an new IDC_CORE::MimeFile
IDC_CORE::MimeFile
object
Array Reference to an array [ ] # reference to an empty array
Structure Reference to an object new <object_class>
CHAPTER 5 163
The initial values can be overridden by passing in a value for a data member in the
argument list to new().
To create an object with default values use:
$var_name = new IDC::schema_name::structure_name;
For example:
$result = new IDC::Util::Iso;
To create an object with passed in initial values use:
$var_name = new IDC::schema_name::structure_name( att_1 => value_1 [, att_2 => value_2, …
] );
For example:
$result= new IDC::Util::Iso( nu => .3, e => 30.0 );
The test() method validates that the generated code performs correctly. It uses the
testInit() function to set the data members to values different from the default. (for
example, setting array attributes to actual arrays of values instead of empty arrays).
The testMethods() method validates that the package
IDC_CUSTOMIZATION::schema_name::structure_name exists and that each method
works when passed a test object.
The AUTOLOAD method is used to provide simple data member access and
modification methods. These methods are utilized in the following section. The access
and modification methods take the form of
• $obj->attribute_name for access
• $obj->attribute_name($value) for modification
The methods newFromXmlFile(), readXml(), writeXmlFile(), and writeXml() are used
to communicate data between Perl and XML files.
• The method newFromXmlFile() creates a new object and initializes the
values to those found in the XML file. It takes a single string argument
containing the XML file name.
• The method readXml() is used by the newFromXmlFile() method. In
addition, it is used by the readXml() method of other objects that contain the
current one.
• The method writeXmlFile() writes an object to a XML file. It takes a single
string argument containing the XML file name.
• The method writeXml() is used by the writeXmlFile() method. In addition, it
is used by the writeXml() method of other objects that contain the current
one.
164
A package IDC::Test is generated in the file

<emv_root>/external_functions/idc_perl/IDC/Test.pm. This package contains a
single function runTest() that in turn calls the test() and testMethods() functions for
each of the packages generated.
Step 3: Write Perl Functions

After the code has been generated, the required customized functions must be written.
For each customized view structure or database entity, a Perl package named:
IDC_CUSTOMIZATION::<schema_name>::<struct_name> must be created in the
file:
<emv_root>/external_functions/idc_perl/IDC_CUSTOMIZATION/<schema_name>/<str
uct_name>.pm.
This package can be developed with the generated Perl packages, MSC Enterprise
Mvision utility packages located in <emv_root>/external_functions/idc_perl, and
any Perl package available.
The MSC Enterprise Mvision utilities packages are IDC_CORE::MimeFile and
IDC_CORE::EngValue.
The package for view structures should contain the implementation of the action
methods defined for the view. Each action function has a single argument which is a
reference to the object being operated on. Each action function should return a
reference to an IDC_CORE::MimeFile object.
View structure packages should be similar to the following:
Package IDC_CUSTOMIZATION::<schema_name>::<struct_name>;
use IDC::<schema_name>::<struct_name>;
use IDC_CORE::MimeFile;
sub <action_1_name>
{
my $self = shift;
my $result = new IDC_CORE::MimeFile;
#
# Write to file
#
return $result;
}
For example:
package IDC_CUSTOMIZATION::Util::Iso;
CHAPTER 5 165
use IDC::Util::Iso;
use IDC_CORE::MimeFile;
sub writeMat1 {
my $self = shift;
$result->mime_type( "txt" );
my $fh = $result->file();
print $fh "MAT1 " . $self->e . ", " . $self->nu . "\n";
return $result;
}
sub writeFile {
my $self = shift;
$result->mime_type( "txt" );
my $fh = $result->file();
print $fh "MAT1 " . $self->e . ", " . $self->nu . "\n";
return $result;
}
1;
The package for database entities contain the implementation of the view mapping
methods defined for the view. Each view mapping method has a single argument
which is a reference to the object being operated on. Each action function returns a
reference to the mapped view object.
The package for database entities should be similar to the following:
Package IDC_CUSTOMIZATION::<schema_name>::<struct_name>;
use IDC::<schema_name>::<struct_name>;
use IDC::<view_1_schema_map>::<view_1_name>;
use IDC::<view_2_schema_map>::<view_2_name>;
sub <view_1_name>
{
my $self = shift;
my $result = new IDC::<view_1_schema_name>::<view_1_name>;
#
# Do mapping
#
return $result;
}
166
For example:
package IDC_CUSTOMIZATION::mil17a::ENVIRONMENT;
use IDC::mil17a::ENVIRONMENT;
use IDC::Util::Iso;
sub Iso {
my $self = shift;
my $result = new IDC::Util::Iso;
# Check if material has any property rows

if( $#{ $self->PROPERTY_rows } >= 0 )
{
# Get the first property
my $prop = $self->PROPERTY_rows->[0];
# Get the value of E11T

$result->e( $prop->E11T->value );
}
return $result;
}
The implementation of the methods are required to access and modify the data
members of objects.
Data members can be accessed using $self->attribute_name.
The type of value returned depends on the type of attribute as shown in the following
table:
Attribute Values Returned
Value type: Access methods:

String $self->attribute_name returns a string.
Integer $self->attribute_name returns an integer number.
Double $self->attribute_name returns a double-precision number.
EngValue $self->attribute_name returns a reference to an
IDC_CORE::EngValue object.
$self->attribute_name->value returns a double precision number.
$self->attribute_name->precision returns a integer indicating the
precision of the number.
$self->attribute_name->units returns a string for the units of the
value.
CHAPTER 5 167
Attribute Values Returned (Continued)

MimeFile $self->attribute_name returns a reference to an
IDC_CORE::MimeFile object.
$self->attribute_name->file returns a reference to a IO::FILE (file
handle) object .
$self->attribute_name->mime_type returns a string for the mime
type of the file.
Array $self->attribute_name returns a reference to an array.
$#{ $self->attribute_name } returns the max index in the array.
$self->attribute_name->[i] returns the ith element of the array for
each my $element ( @{$self->attribute_name} ) {} iterates on
elements of the array.
Structure $self->attribute_name returns a reference to an object.
$self->attribute_name->subattribute_name returns the value of a
subattribute.
Class members can be set using $self->attribute_name( value ).

How a value is set depends on the type of attribute as shown in the following table:
Value Set for Types of Attributes

String $self->attribute_name( “Example Value” ).
Integer $self->attribute_name( 20 ).
Double $self->attribute_name( 20.0 ).
EngValue $self->attribute_name( $eng_value ) set the value to
reference another IDC_CORE::EngValue object.
$self->attribute_name->value( 20.0 ).
$self->attribute_name->precision( 2 ).
$self->attribute_name->units( “Mpa” ).
168
Value Set for Types of Attributes (Continued)

MimeFile $self->attribute_name( $mime_file ) set the value to
reference another IDC_CORE::MimeFile object.
$self->attribute_name->file( $file_handle ) .
$self->attribute_name->mime_type( “text/plain text” ) .
Array $self->attribute_name( $array_value ) set the value to
reference another array.
$self->attribute_name->[i] = $value set the value of the ith
element of the array.
push( @{$self->attribute_name}, $value );push a value to
the end of array.
Structure $self->attribute_name( $struct_ref ) set the value to
reference to another object.
$self->attribute_name->subattribute_name( $value ) set
the value of a subattribute.
Step 4: Test Perl Functions

There are three Perl scripts available in the directory
<emv_root>/external_functions/dc_perl/test to help test the customization:
testEmvPerl.pl, testClass.pl, debugExample.pl.
The testEmvPerl.pl script executes a generated test function (IDC::Test::runTests) that
validates the Perl customization. The script can be executed by typing in a shell
window “perl testEmvPerl.pl”. The script validates both the generated and user
written code for all of the Perl packages.
Contents of testEmvPerl.pl:
use lib "<emv_root>/external_functions/idc_perl";
use IDC::Test;
IDC::Test::runTest();
Example message from running test script:

Testing IDC::Util::Iso ...PASSED
Testing methods in IDC_CUSTOMIZATION::Util::Iso
...PASSED compile
writeFile ...PASSED
writeMat1 ...PASSED
Testing IDC::mil17a::ENVIRONMENT ...PASSED
Testing methods in IDC_CUSTOMIZATION::mil17a::ENVIRONMENT
...PASSED compile
Iso
CHAPTER 5 169
...PASSED
The testClass.pl file is an example script to execute the test functions on a single
package. To test a particular package, the testClass.pl file must be copied and
modified to refer to the package to be tested.
Executing the testClass.pl script does not print the reason for the test failure.
Contents of testClass.pl:
#
# testClass.pl
#
# This perl script is used to test the methods in
# IDC_CUSTOMIZATION::mil17a::ENVIRONMENT.
#
# It's purpose is to test a specific class and its
customizations
#
# Specify the library path for the IDC perl packages
# Use generated package
use IDC::mil17a::ENVIRONMENT;
# Executed test methods
IDC::mil17a::ENVIRONMENT::test();
IDC::mil17a::ENVIRONMENT::testMethods();
If the tests on the generated code fail, please contact your MSC.Software
representative.
If a test on user-written code fails, use the debugExample.pl script to determine the
nature of the problem. The debugExample.pl script is an example script to execute the
user-written function directly.
To debug a particular package, copy and modify the debugExample.pl script to refer
to the package to be debugged. Calls to the methods to be tested must be added. If
there are problems in the execution of the debugExample.pl script, then Perl prints
the reason for the problem.
Contents of debugExample.pl:
#
# debugExample.pl
#
# This perl script is used to debug the methods in
# IDC_CUSTOMIZATION::Util::Iso.
#
# It purpose is to allow the IDC customization methods to be
debugged.
#
# Specify the library path for the IDC perl packages
# Use the package being debugged
170
use IDC_CUSTOMIZATION::Util::Iso;
# Create an test object
$input = IDC::Util::Iso->new();
# Initialize values
$input->testInit();
# Execute function to be tested
IDC_CUSTOMIZATION::Util::Iso::writeMat1( $input );
Step 5: Use Customization in MSC Enterprise Mvision.

After the customization has been validated, it can be used within the MSC Enterprise
Mvision system. The view mappings added to database entities appears as available
views in the CAE Export Target page. The actions defined for the view structures are
available in the CAE Export page when the particular view is selected. When an action
is selected, the Perl code associated with the action is executed.
Customizing Export Using C

This section describes how to use the MSC Mvision export customizations for use with
MSC Enterprise Mvision. The standard set of MSC Mvision export functions are
available for both UNIX/Linux and Windows XP platforms and are included in the
delivery as <emv_root>/external_functions/expfunc. In addition to this set of export
functions, there is another set that will handle secant issues to export functions. This
second set is included in the delivery as
<emv_root>/external_functions/expfunc_secant. These export function sets can be
used interchangeably. No modifications are required to the MSC Enterprise Mvision
system to use the standard set of Export functions on Windows XP or UNIX/Linux
platforms.
Creating, customizing, or converting Export functions, written in the C programming
language, for use with MSC Enterprise Mvision involves the following steps:
1. Build the Export external function using the existing (UNIX) template and C
source files.
2. Copy the Export external function executable into the appropriate MSC
Enterprise Mvision location.
3. Activate the Export customization in MSC Enterprise Mvision system.
These steps are outlined in detail as follows:
Step 1: Build the Export External Function

To create an original Export function refer to the MSC Mvision Builder and Evaluator
User’s Guide and Reference, Appendix C, for detailed instructions. If you are using MSC
Enterprise Mvision on a UNIX platform, you can ignore the remainder of Step 1 and
can directly use the executable created as instructed for MSC Enterprise Mvision
CHAPTER 5 171
Builder. If you are using MSC Enterprise Mvision on an Windows XP platform, then
you must use the “C” files created as instructed for MSC Enterprise Mvision Builder
and perform the following:
On the Windows XP platform, to build an export external function requires the
Microsoft Visual Studio 6.0 complier and linker. A build environment can be created
using the following steps:
• Use a shell or Windows Explorer to create a new folder named my_export in:
<emv_root>/external_functions/mv_export:
i.e. <emv_root>/external_functions/mv_export/my_export
• Copy your (UNIX/Linux) template and “C” files that make up the external
function into the newly-created folder.
The Export external functions must initially be built by using the bat file,
<emv_root>/external_functions/mv_export/bin/MakeExpfunc.bat. This script
generates another specific bat file named Makefile.bat for recreating your
expfunc.exe executable. This is similar to the UNIX Makefile used for MSC Mvision
Builder.
• In the my_export folder, start up a shell program to execute the bat script
MakeExpfunc.bat.
<emv_root>/external_functions/mv_export/bin/MakeExpfunc.bat
• If compile or link errors occur, edit the source files and run the Makefile
generated from the initial bat script.
<emv_root>/external_functions/mv_export/my_export/Makfile.bat
Step 2: Copy the external function executable.

In order for MSC Enterprise Mvision to access the external function generated in the
previous step, the executable must be copied into the
<emv_root>/external_functions directory. The executable must be named
<export_server_name>.exe for the Windows XP platform where
<export_server_name> corresponds to the server name specified in the export
template file.
Step 3: Customize using MSC Enterprise Mvision.

After the customized files (template and mapping files) and export external function
executables have been placed in the appropriate directories, they can be used within
the MSC Enterprise Mvision system. Template files must be in the
<emv_root>/external_functions directory and the mapping files must be in the
172
The view mappings are communicated to MSC Enterprise Mvision through the
databank mapping file. The view appears in the CAE export page. The export
template file defines the structure of the views. In addition, the CAE export template
files define a single action for each view.
The action defined for the view is available on the CAE export page when the view is
selected. When the action is selected, the export external function executable
associated with the action is executed. The file generated by the Export external
function can then be viewed and/or downloaded from the browser.
Note: If converting an existing MSC Mvision Export function or creating a new

function the associated <databank>.mapping file located in the
<emv_databases_dir> directory must include this Export function and the
associated <export_server_name> template must be included in the
<emv_root>/external_functions directory.
Displaying Mvision Figures/Messages via Export

MSC Enterprise Mvision has the capability of displaying Mvision figures or messages
from an export function. This feature provides the export function writer with the
ability to generate external curves, or messages and display them as a PNG image in
the MSC Enterprise Mvision system.
A header file named ExportExternalFigure.h located under
<emv_root>/external_functions/mv_export/include is provided to describe the methods
and structures that need to be included in the export function. A parameter named
DATAFILE is available in the export template. This parameter specifies that Mvision
figure/message data exists, and that the data will be written out to a new export data
file from the export function.
The export function creator is required to write the string
$$EXPORT_CURVE_DATA$$, or $$EXPORT_CURVE_DATA$$-INDEX$$ in the
export output file, wherever Mvision figure/messages are to be displayed. The first
form of the string ($$EXPORT_CURVE_DATA$$) should be used when all figures
written by the export function are to be displayed in the same PNG image. The second
form of the string ($$EXPORT_CURVE_DATA$$-INDEX$$) should be used when
the figures written by the export function are to be displayed as individual PNG
images. The INDEX portion of the string should be replaced by the corresponding
numeric figure number of the PNG image to be displayed.
For example, when $$EXPORT_CURVE_DATA$$-3$$ is encountered in the export
output file, the third figure from the export data file will be displayed as a PNG image.
These strings can be intermixed within export output written by the export function.
When the export function is invoked, MSC Enterprise Mvision replaces the above
mentioned strings in the exported output with a PNG image of the Mvision
figure/messages (obtained from the export data file). A sample template with the
datafile parameter, and a sample of code segment from an export function that
generates external curves follows:
CHAPTER 5 173
Sample Template with Datafile Parameter

HEADER MyExport "Symmetry";
HEADER Test "Dependencies";

TEMPLATE None "Myexpfunc" "my_export_function";
FILENAME : "Output Filename" STRING;
DATAFILE : "Ext Data Filename" STRING;
MID : "Material ID (MID)" INTEGER;
E : "Young's Modulus (E)" REAL;
NU : "Poisson's Ratio (NU)" REAL;
RHO : "Density (RHO)" REAL;
ALPHA : "Thermal Expansion Coefficient (A)" REAL;
TREF : "Reference Temperature (TREF)" REAL;
GE : "Structural Damping Coefficient (GE)" REAL;
ST : "Stress Limit in Tension (ST)" REAL;
SC : "Stress Limit in Compression (SC)" REAL;
SS : "Stress Limit in Shear (SS)" REAL;
MCSID : "Material Coordinate System ID (MCSID)" INTEGER;
K : "Thermal Conductivity (K)" REAL;
CP : "Specific Heat (CP)" REAL;
END_TEMPLATE;
END_HEADER;
END_HEADER;
174
Sample Code for Generated External Curve

#include "ExportExternalFigure.h"
void * my_export_function (void input_data)

{
MyExport_Test_None a;
void *return_data;
int i, n_records;
FILE **files, *dat_file;
char *filenames, fname[FILENAME_LENGTH];
...
FigureErrorstatus;
ErrorData err;
Figure*fig;
FigureCurves curves[4];
doublexCoords[] = {30.7887, 117.165, 233.745, 317.489, 367.393, 433.368, 506.412, 572.267,
618.3, 648.111};
doubleyCoords[] = {99.9112, 95.8308, 93.8191, 91.541, 87.3643, 77.2756, 63.2524, 51.0398,
42.9486, 38.1552};
doublexScatter[]= {27.5294, 86.4622, 142.168, 193.789, 252.116, 292.221, 332.583, 373.842,
427.261, 471.567, 507.59, 536.579};
doubleyScatter[]= {98.8258, 88.223, 78.949, 72.4369, 66.6613, 64.1956, 62.9704, 61.9436,
59.9718, 57.583, 55.7585, 52.7723};
doublexRange[] = {100.5, 100.5, 200, 400};
doubleyRange[] = {44.25, 60, 50, 50};
doublexRunOut[] = {650, 700, 600};
doubleyRunOut[] = {90, 80, 100};
...
/* ---------------------------------------------------------------------- */
EfAllocReturnData( 1, 1, &return_data );
/* ---------------------------------------------------------------------- */
/* Find out how many materials are to be exported, and */
/* acquire memory to store filenames and file pointers. */
ExportGetNumRecords( input_data, &n_records );
/* ---------------------------------------------------------------------- */
/* Find out the name that the user gave us for the first material. */
/* If the first filename is NULL, choose a default name. */
OPEN_FILES( input_data, &filenames, &files, "NASTRAN", "NASTRAN", "$ ", "" );
/* Now start the loop on material records to do the actual export */

fig = (Figure *) malloc (n_records * sizeof(Figure));
for ( i=1; i<=n_records; i++ )

{
ExportWriteOutRecordComment( files[i-1], input_data, i, "$ ", "" );
FillOut_MyExport_Test_None( input_data, i, &a );
fig[i-1].sXAxisName= "TEMP";
fig[i-1].sYAxisName= "%YS_B";
fig[i-1].sFigDescription= "Temperature; Percent Room Temperature Modulus";
fig[i-1].nXAxisType= LINEAR;
fig[i-1].nYAxisType= LINEAR;
fig[i-1].sXAxisUnit= "deg_C";
fig[i-1].sYAxisUnit= "%";
fig[i-1].nCurves= 1;
CHAPTER 5 175
curves[0].nPlotCode= SOLID_CURVE;
curves[0].nRunOutFlag= FALSE;
curves[0].nCurvePoints= 10;
curves[0].dXCoords= xCoords;
curves[0].dYCoords= yCoords;
curves[1].nPlotCode= SCATTER_POINTS;
curves[1].dXCoords= xScatter;
curves[1].dYCoords= yScatter;
curves[2].nPlotCode= RANGE_BARS;
curves[2].dXCoords= xRange;
curves[2].dYCoords= yRange;
curves[3].nPlotCode= RUN_OUT_POINTS;
curves[3].dXCoords= xRunOut;
curves[3].dYCoords= yRunOut;
fig[i-1].curveList= &(curves[(i-1) % 4]);

...
fprintf(files[i-1], "$$EXPORT_CURVE_DATA$$-%d$$", i-1);

}
strcpy (fname, a.DATAFILE.value);

dat_file = fopen (fname, "w");
status = genXmlFromFigure (dat_file, n_records, fig);

if (status != FIGURE_NO_ERRORS)
{
err.sErrName = "FIGURE DATA ERROR";
err.sErrDesc = "Error Description";
err.sErrMsg = getFigureStatusMsg (status);
genFigureErrMsg(dat_file, &err);
}
free (fig);
fclose (dat_file);
...
fprintf(files[i-1], "$\n" );
fprintf(files[i-1], "$ This record will be written as an "
"isotropic material with\n$ constant elastic "
"properties.\n" );
fprintf(files[i-1], "$\n" );
...
}
176
Explicit Non-editable Null Values

Controlling the display and editability of explicit nulls in the MSC Enterprise Mvision
export page and in the Integrated Client Java GUI is supported with export attribute
modifiers. When displaying a material for a particular export target, values display for
the mapped attributes in the page. If a mapped attribute results in a value, that value
is not editable. If the mapped attribute results in a null value, the default behavior of
the system is to allow the user to specify a value in the export page for that missing
value. In some situations, the null value can be actually considered a value and should
not be editable, similar to how actual values are handled. To control this behavior, an
attribute field modifier is added to the export attribute mapping in the database
mapping file (for example, demo_metals.mapping). The field modifier is placed after
the mapped attribute name and has the following syntax:
(NonEditableNullValue = "basis like 'b'")
The modifier specifies a condition to apply to the exported record. The condition must
result in a True/False condition. If the condition results in something other than True
or False, such as a condition expression of “basis,” the export will fail. The condition
can contain attributes from the hierarchy, source, and property tables. An example of
how this feature might be useful would be if the source table contained group
information. Records containing this group specification could have certain attributes
that contain nulls made to be not editable. To do this, a modifier needs to be added to
the desired mapped attributes. For example, in the example below, mapped attributes
E, NU, and RHO need to have noneditable null values when the group attribute is
“dev”.
MAPPING MSC_NASTRAN_2001.Isotropic.None;
E (NonEditableNullValue = "group like 'dev'") : "E11T", "E11C";
NU (NonEditableNullValue = "group like 'dev'"): "NU12",
"(E11T/(2*G12))-1", "(E11C/(2*G12))-1";
RHO (NonEditableNullValue = "group like 'dev'"): "DENS";
ALPHA : "INTERP_X(CTE11vsTEMP, TEMP)";
TREF : "TEMP";
ST : "YS11T", "US11T";
SC : "YS11C";
SS : "US12S";
K : "INTERP_X(CTC11vsTEMP, TEMP)";
CP : "INTERP_X(CPvsTEMP, TEMP)";
END_MAPPING;
Attributes ALPHA, TREF, ST, SC, SS, K and CP, have editable values in the Web page.
CHAPTER 5 177
Controlling the display of Export Functions in MSC

Enterprise Mvision's Export Page
The MSC Enterprise Mvision Web interface displays all export targets, regardless of
whether or not they are used specifically for the Integrated Client (IC) system. In some
cases, it is desired to not show all export targets in the Web export page because they
are specifically designed only for the Integrated Client. To control if an export target
displays in the Web export page, set the export function name on the TEMPLATE line
to blank.
HEADER MSC_NASTRAN_2001 "Symmetry";
HEADER Isotropic "Dependencies";
TEMPLATE None "expfunc" "";
FILENAME : "Output Filename" STRING;
MID : "Material ID (MID)" INTEGER;
E : "Young's Modulus (E)" REAL;
NU : "Poisson's Ratio (NU)" REAL;
RHO : "Density (RHO)" REAL;
ALPHA : "Thermal Expansion Coefficient (A)" REAL;
TREF : "Reference Temperature (TREF)" REAL;
GE : "Structural Damping Coefficient (GE)" REAL;
ST : "Stress Limit in Tension (ST)" REAL;
SC : "Stress Limit in Compression (SC)" REAL;
SS : "Stress Limit in Shear (SS)" REAL;
MCSID : "Material Coordinate System ID (MCSID)" INTEGER;
K : "Thermal Conductivity (K)" REAL;
CP : "Specific Heat (CP)" REAL;
END_TEMPLATE;
For example, to remove the “MSC_NASTRAN_2001.Isotropic.None” from the export

target list in the Web page, change the <install_dir>/external_functions
/MSC_NASTRAN_2001.template file as follows:
From:
TEMPLATE None "expfunc" " write_nastran_iso_none";
To:
TEMPLATE None "expfunc" "";
To see this behavior in the Emv system, restart the EmvServer. Then, select a material
from the material list and display it in the export page. The export target list will
contain this name by default. To filter this name from the export page’s target list,
navigate to the Data Display Options page. Set the Filter Export Targets option to Yes,
and then return to the export page. The MSC_NASTRAN_2001.Isotropic.None selection
178
will not be in the list. If this is the desired default behavior, in the login page set the
new EMV tag FILTEREXPORTTARGETS to true. To change this behavior, change the
following tag specification in the <install_dir>/html/mv3x/Login.html,
<install_dir>/html/alt_mv3x/Login.html or
<install_dir>/html/simple/Login.html files:
From:
<INPUT TYPE="HIDDEN" NAME="FILTEREXPORTTARGETS" VALUE="false">
To:
<INPUT TYPE="HIDDEN" NAME="FILTEREXPORTTARGETS" VALUE="true">
Log off the system and then log back on. Then, repeat the procedure to display a
material in the export page. Notice that by default, the name is missing the export
target list. To turn off the export target list filtering, set Filter Export Targets to No.
6 Administrative Panel Interface
■ Overview
■ Starting the Administrative Panel Interface
■ Administrative Commands
180
Overview
This chapter includes information about the Administrative Panel Interface. The Panel
Interface allows you to update (invoke changes to user access or system configuration
files) for the MSC Enterprise Mvision system online. Changes can be invoked without
stopping and restarting the server. This means client access is not interrupted. All
active clients are alerted to the changes in real time, and the changes are in effect for
all active users when the individual users log out and then log in again.
Note: The Administrative Panel Interface is used to update MSC Enterprise Mvision
user access and configuration pages. If you modify any of the
<emv_root>/config/.properties or the <emv_root>/web_server_files/config
files, you must stop and restart the MSC Enterprise Mvision servers and/or
web server for these changes to take effect.
CHAPTER 6 181
Administrative Panel Interface
Starting the Administrative Panel Interface

To start the Administrative Panel Interface
1. Type the following in a web browser URL:
http://<hostname>/msc/emv/Admin.jsp
where hostname is the host machine where MSC Enterprise Mvision is installed.
A page similar to the following appears:
Admin Panel
2. Click on the “Connect to Server” link.

This displays the “Connect To Server Panel” that allows you to connect to any
MSC Enterprise Mvision server on the network. A page similar to the following
appears.
182
Connect to Server Panel
3. Type in the host name or IP address of the machine on which a MSC Enterprise
Mvision server is running. If you are using the Administrative Panel on the same
host on which the MSC Enterprise Mvision server is running, you can enter
localhost as the “host name”.
4. Enter the port number that the MSC Enterprise Mvision server is listening on. This
information can be found in the <emv_root>/config/Emv.properties file this is
the value of ooc.boa.port property.
5. After you have supplied the required inputs, click the Connect To Server button.
This causes the Administrative Panel to connect to the specified server. A status
message appears at the bottom of the page.
On a successful connection, the following text appears:
Status of action 'Connect To Server' : Success
On a failure, an error message appears similar to the following message:
Status of action 'Connect To Server' : The connection to the Emv Server is
currently not established or not functioning. Re-establish connection to the Emv
Server and verify that the Emv Server is running properly.
The previous error message indicates that the MSC Enterprise Mvision server is
not running properly. To correct the problem, restart the MSC Enterprise Mvision
server and repeat the above procedure again.
CHAPTER 6 183
Administrative Commands
After you have established a connection between the Administrative Panel and a active MSC
Enterprise Mvision server, the following commands are available to update the system online.
Update Users
The Update Users command reloads the SecUser.txt, SecQuery.xml and UserList.txt files
enabling log on and group access. If a user is currently logged on and is removed from the
SecUser.txt or UserList.txt files, the user is allowed to complete the current session, but
is not allowed to log back into the system. The removed user will get an unauthorized message
on login. If an active user is allowed access to new groups by updating the system, the access
to these added groups is not available until the user logs out and logs in again.
The functionality for reloading the SecUser.txt is currently supported in the Security API
provided with MSC Enterprise Mvision. Because the Security API can be customized on a
site-by-site basis using the Security API framework provided, the SecUser.txt file may not
be reloaded nor used. This depends on the customization of the SecurityAPI for your specific
site. Check with your MSC Enterprise Mvision System Administrator.
Adding a valid user to the system requires that each user has an authorization line in both the
SecUser.txt and UserList.txt files that specifies the default group, default units and
allowed groups. If a default user “*” has been implemented in the UserList.txt file, then the
system uses the listed default group, units and allowed groups for any user name not specified
in the UserList.txt file.
Update Group Configuration

The Update Configuration command reloads the Databases.txt, GroupConfiguration.txt,
UserList.txt and InitialUrl.txt files. For updates to the GroupConfiguration.txt and
InitialV.1.txt files active users are unaffected by the update. But the changes for the user’s
configuration will take effect after the user logs off and back into the system. For changes to
the Databases.txt file, all users connected to databanks that are removed from the
Databases.txt are alerted and removed from the system immediately.
184
Reload Databanks
The Reload Databanks command displays a page, similar to the page shown below. This page
allows you to select databanks to reload. The page provides options to notify the users
connected to these databanks that the change is either a change to the databank's data or to its
schema (structure).
Reload Databanks Panel
The Databanks list displays the data source names of the available databanks listed in the
Databases.txt file. Its important to note that the databanks visible to the users are collected
from the navigation views for each group that the individual user has access to use. The listing
in the Reload Databanks Panel is a list of all databanks in the Databases.txt file, not just the
databanks for a specific user. You can select one or more databanks to update. Select the
Update Type for either Data Only or Schema and Data as required.
• Data Only indicates that the data in the database changed but the schema
did not. This includes adding, deleting or modifying data but not adding,
deleting or changing any of the attribute or table definitions. This is the usual
case when the command is applied. The result is to reload the selected
databanks and modify the states of each user connected to these databanks.
This includes clearing selected rows, queries and displaying the
DatabaseUpdatedDataOnly.html template page. Use this option to update
databank support files such as .unt and .mapping files.
The DatabaseUpdatedDataOnly.html page contains the functionality to
determine the next page and how it displays. Each implementation requires
this page to handle the Database Update Data Only function.
CHAPTER 6 185
• The Schema and Data option indicates that anything could have changed in
the databank. When the command is applied the result is to reload the
selected databanks and remove all users that are connected to these
databanks from the system. This requires that the users restart their sessions.
The DatabaseUpdatedSchemaAndData.html page displays and controls
the next action. Each implementation requires this page to handle the
Database Update Schema and Data function.
After the databanks and the databank update type have been selected, click the Update
Databanks button. This notifies all the connected users that the update has occurred
by displaying the corresponding update notification page on the next page request for
each user.
To return to the main panel, select the link Back To the Main Panel link.
Note: When using the Administrative Panel Interface, a user name/password dialog
box may appear that requires you to type in a valid user name and password.
See the sections of this guide for information on LDAP and restricting access to
URLs using the iPlanet web server.
186
A Installing FLEXlm
■ Overview
■ Installing FLEXlm for a New UNIX/Linux Server
■ Installing FLEXlm on a New Windows XP Server
■ Replacing Codes on an Existing UNIX/Linux Server
■ Replacing Codes on an Existing Windows XP Server
■ Installing FLEXlm Using a Nodelock File
■ MSC_LICENSE_FILE vs LM_LICENSE_FILE
■ Additional Documentation
188
Overview
The following steps are a summary of FLEXlm installation procedures for MSC
Enterprise Mvision. For more specific information, or information on integration with
other products using FLEXlm, consult the FLEXlm documentation. See Additional
Documentation on page 195.
When MSC Enterprise Mvision executes, it locates the FLEXlm license file, license.dat,
which contains the name of the FLEXlm license server node and the port number with
which to communicate with the license manager daemon, lmgrd.
The lmgrd daemon determines what node and port are associated with the vendor
daemon, msc, and returns that information to the MSC Enterprise Mvision system.
The application then contacts the vendor daemon which grants licenses if they are
available.
Note: FLEXlm licensing for MSC Enterprise Mvision requires that a valid license be
available for the application and all MSC Mvision databanks. If FLEXlm is
currently installed at your site and the FLEXlm license server is available on the
platform for which MSC Enterprise Mvision is installed, you can integrate the
MSC Enterprise Mvision license with the existing license file and set the
MSC_LICENSE_FILE environment variable on the MSC Enterprise Mvision
host platform to the required <port>@<hostname>. This can be set on
Windows XP platforms using Control Panel/System/Environment.
APPENDIX A 189
If you install MSC Enterprise Mvisionon a Windows XP platform, you can select
FLEXlm during the install/setup process and use the “Setup Wizard” (as shown
above) to install the FLEXlm software on your machine, or to configure the installation
to use an existing FLEXlm license server.
If you install MSC Enterprise Mvisionon a UNIX/Linux platform and you need to
install the FLEXlm server software on this platform select the FLEXlm product option
during the mscsetup process and follow the instructions provided by the mscsetup
script.
Installing FLEXlm for a New UNIX/Linux Server

The following are the steps required to install FLEXlm on a new UNIX/Linux server
and enable MSC Enterprise Mvisionfor operation.
Obtain an MSC Enterprise Mvision License File for Your

Server
To obtain a license file from MSC.Software, you must determine the hostid of the
machine that will be your license server. On UNIX/Linux workstations the mscsetup
utility obtains this information for you, or you can run the lmhostid utility:
# <installation_dir>/bin/lmhostid
You can also use the mscsetup utility to create an Authorization Request form. Send
this form to your MSC.Software sales representative to obtain your permanent license.
Place the License File on the Server

The mscsetup utility automatically installs the license.dat file if you provide it
during installation.
If you have other existing FLEXlm products you may need to integrate the new MSC
Enterprise Mvision license. See Additional Documentation on page 195 for documents
that provide instructions and information.
The license file may be located anywhere on your license server. MSC recommends
installing it in a common location:
/msc/flexlm/licenses/license.dat
190
Verify Paths and Server Names in the license.dat File

Verify that the license.dat file for your installation contains the correct server and
port settings for your site specific installation.
Below is an example of a typical MSC license.dat file.
------Begin File--------
# The authorization line length has necessitated display on multiple
# lines. A “\” is used to signify a line continuation. Please enter
“\”
# continuation character. The VENDOR_STRING field on a feature line must be
# entered on one line only, and not span more than one line.
SERVER UNKNOWN 72767c4d 1700
DAEMON MSC /user_defined_path/msc
FEATURE M_MATERIALS_EVALUATOR MSC 2000.0801 01-AUG-2000 5
5C22EC5AE79928E63033 \
FEATURE M_MATERIALS_SELECTOR_DB MSC 2000.0801 01-AUG-2000 600

CC0207085167EC550247 \
---------End File----------
The first 5 lines license.dat file are comments. These lines can be removed or
ignored.
The 6th line license.dat file is the SERVER line:
• SERVER must be in all caps, followed by the hostname, the lmhostid, and the
port the daemon runs on.
• The hostname can be determined by typing “hostname” on the machine you
are using as your license server. Replace “UNKNOWN” in the license.data
file with this hostname.
• To verify the Imhostid, execute a program with the argument “ id.” If the
lmhostid is not correct, new license codes must be generated. Contact your
local MSC Software Sales Representative.
• The port is set to 1700 by default, but can be any valid port. If you don’t know
which ports are valid, use the default.
The 7th line in the license.data file is the DAEMON line.
• DAEMON must be in uppercase characters, followed by MSC which also
must be in uppercase. The third field on this line is the path to the msc
vendor daemon executable. The vendor daemon executable is found in the
FLEXlm directory. If your installation directory is /msc, then this executable
is found in /msc/flexlm/<arch>/msc where <arch> is machine dependent
term.
APPENDIX A 191
The following is an example of a modified license.data file for a license server running
on a Solaris platform. In this example, the server name is kasane, the installation
directory is /msc, and the port number 1701 is used.
# The authorization line length has necessitated display on multiple
# lines. A “\” is used to signify a line continuation. Please enter
# the codes exactly the way they are printed, including the “\”
# continuation character.The VENDOR_STRING field on a feature line must be
# entered on one line only, and not span more than one line.
SERVER kasane 72767c4d 1701
DAEMON MSC /msc/flexlm/solaris/msc
FEATURE M_MATERIALS_EVALUATOR MSC 2000.0801 01-AUG-2000 5
5C22EC5AE79928E63033 \
FEATURE M_MATERIALS_SELECTOR_DB MSC 2000.0801 01-AUG-2000 600
CC0207085167EC550247 \
Start the Manager Daemons

On the license server, start the license manager daemon with the FLEXlm scriptL
% <flexlm_root>/bin/flexlm lmgrd
Using the ‘lmgrid’ argument do not execute this as root, it may create a security risk
on your network If the license.dat file is located in <flexlm_root>/flexlm/licenses,
this script starts the following daemons:
• lmgrd - the server daemon
• msc - the vendor daemon
Set the lmgrd Daemon to Execute on Reboot

To enable the FLEXlm daemon to automatically start on reboot you must edit the
/etc/inittab (for the appropriate file for your system) on the FLEXlm server as
follows.
Modify the /etc/inittab script to start the lmgrd daemon as a user (this is all one
line):
msc1:23456:once:su username -c ’(umask 022; <installation_dir>/bin/lmgrd -c
<license_path> -l <log_file>)’
Where license_path is the location of the license.dat file (that is,

/<flexlm_root>/licenses/license.dat), and log_file is a file name to which the
daemon will write messages.
192
Set up Clients to Access a Floating License

You have two options for setting the file location on clients:
Note: In the case of MSC Enterprise Mvision, the term client refers to the platform on
which MSC Enterprise Mvision is installed.
• Make the license.dat file available on each client. The default location is
/<flexlm_root>/flexlm/licenses/licenses.dat.
• Set the MSC_LICENSE_FILE environment variable to <port>@<hostname>.
Installing FLEXlm on a New Windows XP Server

The following are the steps required to install FLEXlm on a new Windows XP server
and enable MSC Enterprise Mvisionfor operation.
Obtain an MSC Enterprise Mvision License File for Your

Server
To obtain a license file from MSC.Software, you must determine the hostid of the
machine that will be your license server. Execute the setup.exe utility from the CD
ROM and choose FLEXlm installation. Your system’s lmhostid will be displayed on
this form. Provide this value to your MSC.Software sales representative to obtain your
permanent license.
Important: A Windows XP workstation must have a network card and a functioning

TCP/IP protocol to use a FLEXlm license server.
Place the License File on the Server

The FLEXlm installation setup.exe utility automatically prompts you for all required
information and installs the license.dat file if you provide it during installation.
If you have other existing FLEXlm products you need to integrate the new MSC
Enterprise Mvision license. See Additional Documentation on page 195 for documents
that provide instructions and information.
The license file may be located anywhere on your license server. MSC recommends
locating it in a folder named: <msc>\flexlm\licenses\license.dat.
Verify the FLEXlm Control Panel Icon

After the FLEXlm installation procedure has completed, you should have a FLEXlm
icon in the Control Panel. This control panel allows you: to start and stop the license
manager, check the license.dat file, and perform FLEXlm diagnostics.
APPENDIX A 193
Set up Clients to Access the Floating License

The MSC_LICENSE_FILE environment variable informs MSC Enterprise Mvision
where to obtain licenses. It can be set in Control Panel\System\Environment either
with the path and file name to the license.dat file, or <port>@<hostname>.
Replacing Codes on an Existing UNIX/Linux Server

Follow these steps if you have an existing MSC Enterprise Mvision installation and
have received new codes (as a renewal, change, and so on).
Important: During this process, users will lose contact with the license server, and
will not be able to access modules, and so on. This should not adversely
affect the system, but it is advisable to have all users exit MSC
Enterprise Mvision until it is completed.
Edit the New License File

Place the new codes as a license file in the same directory as the existing license.dat
file. Name it license_new.dat. Change the SERVER and DAEMON lines in the new
license file to include the same port number, server name, and paths as the existing
file. For example:
SERVER server1 123465 1700
DAEMON MSC /msc/flexlm/bin/msc
Replace License File

Rename the existing license.dat file to license_old.dat, and the new file to the current
license file name (that is, license.dat):
# mv license.dat license_old.dat
# mv license_new.dat license.dat
Force Daemon to Read New License File

Use the lmreread command to cause the lmgrd daemon to reset using the new license
file:
# <installation_dir>/bin/lmreread -c
<path>/license.dat
You should now be able to run MSC Enterprise Mvision products using the new
licenses. If for some reason this fails, stop and restart the daemons as follows:
#<installation_dir>/bin/lmdown -c <path>/license.dat
#<installation_dir>/bin/lmgrd -c <path>/license.dat
194
Replacing Codes on an Existing Windows XP Server

If you have an existing MSC Enterprise Mvision installation and have received new
codes (as a renewal, change, and so on), you must perform the following steps to
enable MSC Enterprise Mvisionwith the new license codes.
Important: During this process, users will lose contact with the license server, and
will not have access to the MSC Enterprise Mvisionserver. This should
not adversely affect databases, but it is advisable to have all users exit
MSC Enterprise Mvision until it is completed.
Edit The New License File

Place the new licensecodes as a file in the same directory as the existing license.dat file
(name the file license_new.dat). Change the SERVER and DAEMON lines in the new
license file as required to include the same port number, server name, and paths as the
existing file. Refer to Verify Paths and Server Names in the license.dat File on
page 190.
Replace License File

Use Windows Explorer to rename the existing license.dat file to license_old.dat,
and the new file to the current license file name (that is, license.dat).
Stop and Restart the FLEXlm Service

Under Start\Settings\Control Panel\FLEXlm, select the Stop to stop the license
service, then select Start to restart it. This should reread the license.dat file and
enable your new licenses. If errors occur, or if the licenses still do not appear to be
available, reboot the system.
Installing FLEXlm Using a Nodelock File

A FLEXlm nodelock license file differs from a network license file with the addition of
a host ID at the end of each FEATURE line.
If you have a temporary or demonstration license it may be supplied as a nodelock
license.dat file. To use this file, set the MSC_LICENSE_FILE environment variable to
the location of this file:
UNIX/Linux
setenv MSC_LICENSE_FILE /<fullpath>/license.dat
APPENDIX A 195
Windows XP
Set the value of the MSC_LICENSE_FILE variable to /<fullpath>/license.dat
under Control Panel\System\Environment.
MSC_LICENSE_FILE vs LM_LICENSE_FILE
By default, all FLEXlm products use the environment variable LM_LICENSE_FILE to
define the location of the license file (that is, license.dat), or the server and port
number (that is, 1700@servername) for floating licenses. This includes MSC Enterprise
Mvision products.
This presents a problem, however, when MSC Enterprise Mvision is used in the same
environment with other products (CAD packages, solvers, and so on) that also use
FLEXlm. If the LM_LICENSE_FILE variable is set to the MSC Enterprise Mvision
license file location, these other products may not locate their licenses correction and
vice versa.
For this reason, all MSC products use their own variable, MSC_LICENSE_FILE, to
identify the location of the license file, or the server and port number for floating
licenses. The MSC.Software Corporation recommends using MSC_LICENSE_FILE for all
MSC products. However, the variables MSC_LICENSE_FILE and
LM_LICENSE_FILE are equivalent.
If both environment variables are set, MSC Enterprise Mvision will use the
MSC_LICENSE_FILE setting first.
If you need more information on LM_LICENSE_FILE, consult the Globetrotter
supplied documentation (see Additional Documentation on page 195).
Additional Documentation
To obtain additional information for FLEXlm products, visit the Globetrotter Web
page. If you have Internet access, set your browser to:
http://www.globetrotter.com/
For additional information on iPlanet Web Server, Enterprise Edition, visit the iPlanet
Web Page. If you have Internet access, set your browser to:
http://docs.iplanet.com/docs/manuals/enterprise.html
196
B Using the Batch Builder
■ Getting Started with Batch Builder

■ Batch Builder Program
■ Running Batch Builder
■ Batch Builder Menus
■ Batch Builder Examples
198
Getting Started with Batch Builder

The Batch Builder program for the Windows XP is a console application that runs in a
shell window. The Batch Builder uses the same FLEXlm security system as MSC
Enterprise Mvision to validate access and manage licenses. No additional software is
required.
The Batch Builder program uses several environment variables that must be set in
order for the program to locate the required files. A variable named MV_PATH is
used to locate databanks stored on the system. A variable named MV_HOME must be
set to allow the program to locate ancillary files. These variables can be set in the
settings\system\environment or on the command line in a shell window using the
following commands:
• setenv MV_PATH .;<emv_root>\databases
• setenv MV_HOME <emv_root>
After the variables are set, you can run MvBatchBuilder.exe from the DOS or CSH
shell window.
Note: The MSC_LICENSE_FILE variable must also be set prior to executing
MvbatchBuilder.exe.
APPENDIX B 199
Using the Batch Builder
Batch Builder Program

The Batch Builder program is primarily designed to build, modify, and populate
databanks. Most of these capabilities are single-item selections with user prompts
which are self explanatory. The Batch Builder Program does support large-scale
databank building.
Batch Builder is run from a MSDOS, C shell window, or command line and is designed
to provide experienced users with the capability of building databanks from shell
scripts or MSC Mvision Builder session files. Most of the functions and operations
found in the Batch Builder program are similar or identical to those performed in the
graphical user interface for MSC Mvision Builder.
The Batch Builder program offers some unique capabilities not available in the MSC
Mvision Builder’s graphical user interface (renaming attributes and relations;
assignment and modification of synonyms; deleting attributes and relations; deleting
data rows by query; and editing of all attribute parameters.)
Exercise caution: The Batch Builder program does not have the same level of error
checking and verification capabilities of the MSC Mvision Builder’s graphical user
interface. Be sure to save a copy of your data before attempting something new or
doing something that may have a detrimental effect on your data.
200
Running Batch Builder

The mvbatchbuilder executable provides a text-only interface for MSC Mvision
Builder functions. The program includes most of the builder functions available in the
MSC Mvision Builder’s graphical user interface, and includes some additional
capabilities for the advanced user. The interface is a set of hierarchical menus and
prompts that lead the user through the basic Builder Functions. In addition, you can
record your actions and use session file commands to drive the interface.
The syntax to initiate mvbatchbuilder is as follows:
<emv_root>\bin\mvbatchbuilder [-init session_file]
[-playback session_file] [-record session_file]
[-b buff_size] [-overwrite]
[-detailed_messages] [-log log_file_name]
The available command options are as follows:

-init session_file Executes the specified session file to initialize the
program.
-playback session_file Plays back the specified session file.
-record session_file Sets the session file recording ON and sets the name of the
session file.
-b buff_size Sets the initial value of the databank buffer size in
kilobytes (default is 10 k).
-overwrite Sets the initial value of the file overwrite ON.
-detailed_messages Sets the initial value of the detailed messages ON. Default
is summary messages
-log log_file_name Sets logging ON and sets the name of the log file.
APPENDIX B 201
Batch Builder Menus

The Batch Builder Menus are a set of hierarchical menus that lead you through the
basic Builder Functions. The majority of these menus are listed below along with a
description of the menu options.
The program does have some query and select capabilities. These capabilities are;
Query and Select options on the Show Databank menu, the batch spreadsheet on the
main menu, and Execute Session File and Type in Command options on the Session
File menu.
The following displays the majority of the Batch Builder Menus and describes each
menu item:
Batch Builder Main Menu

1) Open Databank - Initiates open databank menu.
2) Set Current Databank - Initiates menu to toggle between open databanks.
3) Close Databank - Initiates menu to close databanks from open list.
4) Create Databank - Initiates Create Databank menu.
5) Save Databank - Saves current databank to same name.
6) Save As - Saves current databank to user-defined name.
7) Change Units - Initiates menu to convert databank values.
8) Load Databank - Initiates menu to read data into databank.
9) Dump Databank - Initiates menu to write define/input files.
10) Create databank Index File - Creates index file for current databank.
11) Delete Rows - Initiates menu to delete data rows by query.
12) Show Databank - Initiates menu to list and review attributes and relations.
13) Modify Schema - Initiates menu to create or edit attribute, synonyms, and
relations.
14) Spreadsheet - Initiates textual spreadsheet.
This option can be used in the same manner as the interactive spreadsheet. The
navigation methods are documented in the Building MSC Mvision Databanks and a
help file can be accessed from within the spreadsheet. The syntax for entering data
and commands in cells is the same as is recorded in the session file from the
interactive product with slight modifications. For example: from interactive session
file MvSpreadsheetCommand("A3=‘‘:=select(""mil5.des"",A2:F2,A1)‘‘" ) for
MvBatchBuilder input - A3=‘:=select("mil5.des",A2:F2,A1)‘ in general the command
202
is not quoted and all input must be enclosed within "back tics". See “Spreadsheet
Syntax Example” at the end of this section.
15) Setup - Initiates menu to set log, session, message, and buffer parameters.
16) Session File - Initiates menu to execute or convert session files.
Execute Session File: With this option you can execute any session file created using
the interactive product. This includes any build functions or spreadsheet functions
(general query and browse functions are not recorded in the session file). You may
want to set the "MV_ALLOW_ERRORS_IN_PLAYBACK" variable to 1, before using
this option or the session file terminates on the first error encountered.
Type in Command: This option allows you to type in and execute "any" command
found in a session file from the interactive product. The syntax is the same as it is in
the session file.
17) Exit - Quit program.

Enter Selection (X to exit menu) >
Entering Selections
At the following prompt, enter a selection:
Opening Databanks
Use the following menu to navigate to and open MSC Mvision databanks. Note: Selecting
‘Other’ allows the user to type a directory name in which the program looks for databank files.
Open Databank Menu (Current Directory=<emv_root>\databases)
1) <emv_root>
2) demo_metals.des
3) Show all files
4) Other
APPENDIX B 203
Changing Units
The following menu converts databank values to alternate units systems determined
by the databank.unt file for the current databank.
Change Units Menu
1) Default Units
2) SI-Customary
3) SI-Consistent
4) US-Consistent
Creating Databanks
The following menu creates a databank from a define file or Express schema file.
Create Databank Menu
1) Check Define File
2) Read Define File
3) Read Express Schema File
4) Exit
Loading Data in Databank

The following menu loads data into an existing databank using an input file or
Express data file.
Load Databank Menu
1) Check Input File
2) Read Input File
3) Read Express Data File
4) Exit
204
Writing Define and Input Files

The following menu writes define/input files or Express Schema/data files from an
existing databank.
Dump Databank Menu
1) Write Define File
2) Write Input File
3) Write Express Schema File
4) Write Express Data File
5) Exit
Deleting Data Rows

The following menu deletes data rows from an existing databank using a specified
query.
Delete Rows
Enter query <cr> for no query >
1) Yes
2) No
Showing Databanks
Show Databank Menu
1) Query - Enter query to active set.
Note: The syntax for the query input is the same syntax that is used for the interactive
product. For example: cname such as’*AL*’ or sizeof(_property_rows) > 0
would be valid queries for mil5.des. Note that the query only returns the
"number" of rows found and not the actual data. See “Query Syntax Example”
at the end of this section.
2) Select - Extract specific attribute values.
Note: This option operates in the same manner as the "spreadsheet select" feature in
the interactive product. This option is a "dynamic select", the select is applied
to the entire databank. When a "field" is specified the relation (table), and the
parent relations (higher level tables), that contains that field (attribute) are
automatically retrieved and the specified query is applied to these relations.
For the DPI example "select (material | cname | cname like "*AL*")" you would
APPENDIX B 205
enter the field "cname" and then the query cname like ’*AL*’ (notice the single
quotes). Any field or query that is valid for the interactive spreadsheet select is
valid for this option. Note this option returns a listing of the requested data. See
Select Syntax Example at the end of this section.
3) List Tables - Lists all relation names, type, and number of rows.
4) Show Table - Choose specific relation, list relation and attributes.
5) List Attributes - Lists all attributes and their parameters.
6) Show Attribute - Choose specific attribute and display parameters.
7) List Named Conditions - List named queries.
8) Exit - Quit menu.
Modifying Schema
Modify Schema Menu
1) Create Attribute - Add attribute to databank.
2) Edit Attribute - Modify existing attributes and synonyms.
3) Delete Attribute - Remove attribute from databank.
4) Rename Attribute - Change name of existing attribute.
5) Create Table - Add hierarchy or data relation.
6) Create Subtable - Add a dependent relation.
7) Delete Property Table - Remove data relation from databank.
8) Rename Table - Change name of existing relations.
9) Create Named Condition - Name a query.
10) Delete Named Condition - Remove name from query.
11) Exit - Quit menu.
206
Initiate Spreadsheet
The following menu is a text-driven spreadsheet (enter spreadsheet commands).
Spreadsheet
A B C
+----------------+----------------+----------------+
1
2
3
4
5
+----------------+----------------+----------------+
6
7
Enter spreadsheet command (? for help) <cr> to cancel >
The following are control functions for text spreadsheet.
U n - Up n Rows PU n - Page Up n Pages
D n - Down n Rows PD n - Page Down n Pages
L n - Left n Columns PL n - Page Left n Pages
R n - Right n Columns PR n - Page Right n Pages
CW - Set Cell Width DV - Display Cell Value
DW - Set Display Width DE - Display Cell Equation
DH - Set Display Height DF - Display Cell Format
@ addr - Locate Cell addr to upper left of display
APPENDIX B 207
A B C
+----------------+----------------+----------------+
1
2
3
4
5
+----------------+----------------+----------------+
6
7
Enter spreadsheet command (? for help) <cr> to cancel >
Recording and Logging

The following menu set and controls recording and logging functions:
Setup Menu
1) Set log file name
2) Set session file name
3) Set log file recording flag
4) Set session file recording flag
5) Set detailed message flag
6) Set databank buffer size
7) Set express buffer size
8) Exit
208
Executing and Converting Session Files

The following menu executes and converts session files:
Session File Menu
1) Execute Session File
2) Convert Old Session File
3) Execute Old Session File
4) Convert CLI file
5) Type in command
6) Exit
APPENDIX B 209
Batch Builder Examples

1. Query Syntax Example
Open Databank
materials_selector.des
Show Databank
Query
form like ’*bar’
Query
form like ’bar’ or form like ’sheet’
Query
type like ’*steel*’
Query
type = ’*steel*’ xor type = ’*iron*’
Query
form = ’Bar’ xor form = ’Sheet’
Query
us_t * .8 < 50
Query
density > .26 and poisson_r > .3
Query
cte_lo ex or cte_hi ex or cte ex
Query
ys_t/us_t < 100
Query
ue_t/us_t >1
Query
ra/us_t != 1
Query
h_rc/us_t < 1
Query
form like ’*bar’ or e11t ex
Query
e11t ex and ys_t ex or us_t ex
Query
ys_t ex or us_t ex and e11t ex
Query
(ys_t ex or us_t ex) and e11t ex
Query
ys_t ex and e11t ex
Query
us_t ex and e11t ex
Query
E_T exists
Query
E_T_LO exists
Query
density = .1
Query
density < 0.1
Query
density > .10
210
Query
density <= .1
Query
density >= .1
Query
density != .1
Query
E11t > E22T
Query
E11T/DENSITY > 10
Query
E11T > 20.005
Query
E11T < 20.5
Query
E22T > 20
Query
density .1 <x> 10
Query
type like ’gold’
Query
density exists
Query
ys_t < 17.5
Query
POISSON_R exists
Query
e11t > 10
Query
e11t > e22t
Query
type like ’al*’
Query
test_temp > 65
Query
type like ’woods’
Query
type like ’tin*’
Query
type like ’nylon*’
Query
type like ’*glass’
Query
type like ’cork’
Query
type like ’*steel*’
Query
cname like ’pig tin’
Query
cname like ’*steel*’
Query
cname like ’*steel’
Query
cname like ’steel*’
APPENDIX B 211
Query
cname like (null)
Query
cname like ’*606*’
Query
cname like ’*6?6*’
Query
cname like ’*606?’
Query
cname like ’?606*’
Query
cname like ’10e10’
Query
cname like ’&’
Query
cname like ’(*)’
Query
cname like ’*-t6’
Query
cname like ’$’
Query
canme like ’2*’
Query
property_rows[1].cname
Query
LENGTH (cname) > 10
Query
MECHANICAL.row_id = 2
x
Close Databank
x
2. Select Syntax Example

Open Databank
mil5.des
Show Databank
Select
cname
cp
cname like ’*steel*’ and cp exists

Yes
Select
’CNAME : ’ + cname + ’ UNS : ’ + uns
cname like ’*steel*’

Yes
Select
e11t
ctc11
cname like ’*steel*’ and e11t ex and ctc11 ex

212
Yes
Select
’CNAME : ’ + cname + ’ UNS : ’ + uns
temp
cp
cpvstemp exists and cname like ’*copper*’

Yes
Select
table
table_name
figure
cpvstemp exists and figure ex and cname like ’*steel*’

Yes
x
Close Databank
x
3. Spreadsheet Syntax Example

Open Databank
test.des
Spreadsheet
A1=1
A2=2
A3=3
B1=9
B2=8
B3=7
C1=‘:=sort(B1:B3)‘
cut C1
paste A4:
copy A4
paste B4:
B4= ‘:=sort(C1:C3)‘
B4=‘:=sort(C1:C3)‘
B4=‘:=sort(B1:B3)‘
clear A10
A8=‘CP EX ‘
A9=‘CNAME‘
B9=‘CP‘
A10=‘:=select("test.des",A9:B9,A8)‘
B9=‘CTC‘
B9=‘CTC11‘
A8=‘CTC11 EX ‘
C1=‘:=for(1,10,1)‘
save_as "test.spd"
open "test.spd"
write "test" "w" A1:C6
D1= ‘read("test","")‘
D1=‘:=read("test","")‘
APPENDIX B 213
D1=‘:=read("test","t")‘
‘recomputeall‘
?
D
D 4
U
U 4
R
R 4
L
L 4
CW 10
Cw 20
Cw 16
DW 20
DW 40
DW 10
DH 20
DH 40
DH 12
PD
PD 4
PU
PU
PU 4
PR
PR 4
PL
PL 4
@ D40
@ A1
Close Databank
test.des
x
214
C Troubleshooting MSC Enterprise
Mvision
■ Overview
■ Emv Monitor Fails to Start (Windows XP)
■ Emv Server Starting Repeatedly from the EmvMonitor
■ A Server Fails to Start
■ Large Property Curve/Figure Image Fails to display
■ JSP pages for Administration Panel fails on Windows XP
■ Microsoft Windows Service Fails to Stop Service

■ Downloading Data to Excel Fails to Display the Excel
■ Downloading files to Internet Explorer fails when SSL is enabled
■ Downloading of Emv_Plot_Macro.xla Fails to Download Correctly
to Excel
■ Troubleshooting the Formatted Report Generator
216
Overview
This appendixes describes steps to solve some of the more common problems
encountered with the installation and operation of MSC Enterprise Mvision.
Emv Monitor Fails to Start (Windows XP)

Verify that the JRE’s current version is set to 1.2 or higher.
To verify the version:
• Using the Windows application regedit, verify that the setting of the key
(HKEY_LOCAL_MACHINE\SOFTWARE\\JavaSoft\\Java Runtime
Environment\\CurrentVersion) is set to “1.2”.
If this value is not set correctly, the EmvMonitor may not start properly. Allow the
service to interact with the desktop, which allows you to see the error messages from
the JNT service starter application.
To fix the problem:
• Reinstall JDK 1.2.2 and ensure that the .bat and .properties files in the
<emv_root>/bin and <emv_root>/config directories point to the correct JDK
1.2 directory.
Emv Server Starting Repeatedly from the

EmvMonitor
Check the property ‘check_interval’ in the EmvMonitor.properties file. If the EMV
server is loading several databanks or large databanks that take a long time to load,
the EMV Server may be still loading the databanks when the ‘check-intervac’ ends. In
this situation, the EMV Monitor terminates the EMV Server process and attempts to
restart it.
A Server Fails to Start

Examine the <emv_root>/log/*.txt log files for information for the server that is
failing to start. Verify that the configuration information is correct in the
<emv_root>/config/Databases.txt, <emv_root>/config/GroupConfiguration.txt
files and the associated .properties files.
If EmvServer fails to start, run <emv_root>/bin/Prolog to see if the port that
EmvServer needs to run on is available and clear. Sometimes an old export function
that does not finish will reside in the EmvServer port.
APPENDIX C 217
Troubleshooting MSC Enterprise Mvision
A User Fails to Connect to the Emv Server

Verify the user’s login information in the <emv_root>/config/UserList.txt file.
Verify that the default group and allowed groups are valid groups found in the
<emv_root>/config/GroupConfiguration.txt file.
Large Property Curve/Figure Image Fails to display

Verify that the jcchart363j.jar file is in <emv_root>/jars/ directory. Verify that
the classpath in the EmvMonitor.properties file for the
“figure_to_png_image_server_command” property contains the jcchart363j.jar
file.
Verify that the Figure to PngImage Server is running by viewing the running
processes. There should be one java process for the EmvMonitor and one for the
Figure to PngImage Server.
Review the <emv_root>/log/FigureToPngImageServerLog.txt file and verify that the
server has started up and there are no error messages.
Review the <emv_root>/log/EmvLog.txt file for messages that contain ‘png’. These
messages may contain CORBA connection errors indicating that something is failing
with the configuration.
Verify the Global.properties file settings for the servers and the
FigureToPngServer.properties for the ooc.orb.port setting.
JSP pages for Administration Panel fails on

Windows XP
It is possible that the JSP pages for the Administration Panel fails to display correctly
when the Web Server is running on Windows XP. A known cause is if the initial
reference to these pages is in a case not exactly matching the case of the .jsp files. This
causes the generated Java Servlets from the JSP pages to have incorrect names.
Subsequent requests to the JSP pages fails due to this naming issue.
To fix the problem:
• Go to the <netscape_root>/server4/https-<server name>/ClassCache
directory and delete all the files in this directory.
This is the location of the generated Java Servlets for the JSP pages. Navigate
to the JSP pages using a Web browser and use the case-sensitive names when
accessing the pages. This generates the correct names for the Java Servlets in
the <netscape_root>/server4/https-<server name>/ClassCache directory.
This only has to be done once for each page.
218
Microsoft Windows Service Fails to Stop Service

When stopping the EmvMonitor service from the Services control panel, it is
necessary to press the Cancel button when the status indicator has moved to about the
middle of the status area. This terminates the dialog and also terminates the service. If
you don’t press the Cancel button, the stop service dialog continues to wait for the
service to stop but the service never appears to stop.
APPENDIX C 219
Downloading Data to Excel Fails to Display the Excel

When downloading data to Excel, sometimes Internet Explorer displays in place of
Excel. This is typically seen when Excel to configured to display its files embedded in
the browser and not as a standalone application. To correct this problem, you must
configure Excel to display as a standalone application.
To set Excel as a standalone application:
1. Open a Windows Explorer Window and select the Tools menu.
2. Select Folder Options.

3. Click the File Types tab.
4. Scroll down to the “XLS” extension that is for Microsoft Excel.

220
5. Click the Advanced button to display the options on how “XLS” file types interact
with the Windows environment. The following dialog appears.
6. Clear the selection of the Browse in same window check box, and then click the
OK button.
This tells the Windows environment not to use Internet Explorer to display Excel
spreadsheets when downloading Excel spreadsheets from the Web.
Downloading files to Internet Explorer fails when
SSL is enabled
Sometimes, downloading a file such as a Excel spreadsheet or a full text file fails to
correctly download the file. This is a known issue with Microsoft Internet Explorer.
Microsoft provides a fix on how to resolve the issue with the various browsers. See the
following Microsoft Knowledge Base Article that discusses how to resolve this
problem
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;q323308
APPENDIX C 221
Downloading of Emv_Plot_Macro.xla Fails to

Download Correctly to Excel
If client browsers are unable to download the Emv_Plot_Macro.xla due to the
extension being converted to ‘.xls’, it is possible to configure your Web server to treat
this ‘mime file’ extension ‘.xla’ as a binary file for download.
To configure your Web server:
1. In iPlanet, edit the mime file types in the Web-server configuration and remove
the ‘.xla’ mime file type mapping from the server. This disables the Web server
from telling the web client’s that this is a ‘.xls’ mime file type.
2. To do this, edit the type ‘application/vnd.ms-excel’ and remove the ‘.xla’ mime
file type.
Troubleshooting the Formatted Report Generator
Logo Fails to Display in PDF or HTML
If the path to a company logo image is incorrect or contains spaces or characters (i.e.
%, _, 1, etc.), the PDF hardcopy may not be generated or may be generatd with the path
to the file printed in the footer in place of the image.
Graphics Images Fail to Display in PDF or HTML

(UNIX/Linux)
The are two variables that control the display of images in the formatted PDF and
HTML reports: the FigureToPngImageServer and the graphics capability in LaTeX.
• If images are not generated properly in the EMV browser, they will also not
be generated in the PDF or HTML reports. On UNIX/Linux servers, the
FigureToPngImageServer uses Xvfb to display images, so verify that the X
Virtual Frame Buffer is running on the server that is hosting Enterprise
Mvision. Log into the UNIX/Linux server and type the command:
222
ps -ef | grep -i xvfb

If it is not running, you can start it from the
<emv_install_dir>/bin/.bin directory, which may require root
priveleges.
• It images display correctly in the EMV Browser, but fail to display in the PDF
report, verify that LaTeX is properly installed with the additional ps-tricks
and ps-tricks base components. Review the installation instructions for
LaTeX in Preparing for UNIX/Linux Installation (p. 19).
PDF Report Fails to Display in Browser

There are two main components which need to be functional to display a PDF report
in the Browser: Adobe Reader and the PDF Report Generator. Typical errors include:
• No report generated in the browser window.
• Error message: “Unable to find report generated by external report generator.”
Start by verifying that the path to the LaTeX or MiKTeX bin directory is set correctly.
Then verify that Adobe Reader or Adobe Acrobat is enabled to display in a Browser
window.
To enable reading of a PDF file in your browser, verify configurations in Adobe
Reader and then verify that Adobe is enabled in your browser. Open the Adobe
Reader application and select ‘Preferences’ from the ‘Edit’ menu. Navigate to the
‘Internet’ settings dialog and select “Display PDF in Browser.” In the same dialog box,
select “Internet Properties.” In the Internet Properties dialog box, select “Manage
add-ons”. Under the “Programs” tab, veify that “Adobe PDF Reader Link Helpers”
and “Adobe PDF Reader” are enabled. Close all dialog boxes by clicking “OK.” and
then close the Adobe Reader application. Close the browser window. Reopen the
browser and log into EMV. Select a material for display and then select the “PDF
Report” button. If the PDF report still fails to display, you must troubleshoot the
Report Generator on the Emv Server.
To troubleshoot the PDF Report Generator on the EMV server, enable debugging in
the GeneratePdfReport batch file. Navigate to the <emv_install_dir>/bin
directory and verify that a directory called filesFromLastRun exists. If not, create
the directory. Then open the GeneratePdfReport file. Set the value of the Debug
variable (line 24) to the value “1”. On Windows, also add the following line to the end
of the file:
copy "%TEMPDIR%" "%EMVDIR%"\bin\filesFromLastRun
Open a browser window, log into EMV, select to display a material and “PDF
Report”.Navigate to the <emv_install_dir>/bin/filesFromLastRun directory and open
the log file with a text editor to evaluate the PDF Report Generation process. You will
need to identify errors in this file and attempt to repair the installation. It is suggested
that you open a command window and copy the contents of the filesFromLastRun
directory into a test directory, set the path to the LaTeX or MiKTeX bin directory, and
APPENDIX C 223
step through the execution steps defined in the GeneratePdfReport file. A detailed
description of the PDF Report Generation Process can be found in the MSC Enterprise
Mvision User Interface Implementation Guide.
224
I N D E X
MSC Enterprise Mvision Installation and System Administration Guide
A Configuring MSC Enterprise Mvision for

full text and image attribute viewing 110
Add/modify a group or navigation view 126 Converting databanks for use with MSC
Add/modify a user 124 Enterprise Mvision 108
Admin Server 67 Copying and converting supporting files 109
Global.properties file 67 CORBA 73
LDAP parameters 67 Creating
parameters 67 default navigation views for MSC
Enterprise Mvision 117
the GroupConfiguration.txt from a form
B file 113
Batch Builder Customizing export using Perl 160
examples 209
getting started with 198
main menu 201 D
program 199 Databanks
bin building 197
directory, contents of 35, 37 disclaimers, creating 122
Blowfish, DES,3DES 66 installation 60
Building databanks 197 databases
directory, contents of 35, 37
Databases.txt file 141
C DataList tag, changes to 102
Deliverables, listed 13
CD-ROM drive, removing 47
CD-ROM, mounting 46 Deselect option 51
Directories
Chart Sizes
setting 70 bin 35
config 35
Charts
set maximum generation time 70 databases 35
doc 35
set size 70
config external functions 35
html 35
Config directory 35 install 35
Xvfb 35
Configuration files
about 133 Directories in properties file, list of 37
Disk space 22
Databases.txt 141
GroupConfiguration.txt 133 for user sessions 25
Disk space required 25
Configuraton files
format flags 74
226 INDEX
doc Environment variables 57

directory, contents of 35 Integrated Client 41
Documentation 13 Examples
directory for 35 adding databank to MSC Enterprise
Mvision 129
Batch Builder 209
E columns of data 125
installation messages 53
Emv Monitor
interface implementation 151
interface 77
message from test script 168
parameters 68
query syntax 209
EMV Server
select syntax 211
configuration of 65
spreadsheet syntax 212
configuration parameters 65
tags and statements in
Emv Server 67
GroupConfiguration.txt 138
EMV tags
using links to previous versions 62
DataList 102
Export functions, customizing 170
enhancements and changes 101
External functions 35
GrepDataList 102
external_functions
SELECTEDROWS_0_VIEWS 102
SELECTEDROWS_0_VIEWS_PROPERT
Y 102
using 102
VIEW_0 102 F
VIEW_0_EXPORT 102 FigureToPngImage.properties file 69
VIEW_0_PROPERTY 102 FigureToPngImageServer 67
VIEW_O 102 parameters 69
Emv.properties file 65 properties file 69
EmvHardcopy.properties file 58 setting chart size 70
EmvMonitor
about 77
kill processess 68
on UNIX/Linux platforms 80
Orbacus parameters 68
parameters 67
service (Windows XP) 78
starting manually 80
starting on UNIX platforms 80
starting with inittab 80
EmvMonitor Server 67
EmvMonitor.properties file 67, 77
EmvUserLoginDataAPI.dll 104
Encryption
algorithms 66
settings 66
INDEX 227
FLEXlm html 35
additional information 195 directory, contents of 36, 37
Control Panel icon, checking 192 HTML template files 144
daemon to start on reboot 191
installation overview 188
installing on UNIX server 189
license system 35
I
IDEA 66
license.dat 189, 192
Implementing export functions for MSC
license.dat on UNIX/Linux 193
license.dat on Windows XP 194
install
LM_LICENSE_FILE variable 195
directory, contents of 36
lmgrd 191
Installation
lmhostid 189
device selection 48
lmreread 193
directories 35
MSC_LICENSE_FILE variable 192, 195
Integrated Client (UNIX/Linux) 41
nodelock codes 194
Integrated Client (Windows) 41
replacing codes 193, 194
LaTeX 31
stop and restart service 194
preparing for 19
Windows XP server 192
prerequisites 31
Force daemon to read new license file 193
procedure (UNIX/Linux) 42
Formatted HTML Hardcopy 31
removing CD-ROM 47
selecting directory 49
selecting products for 50
G size of 19
General administration functions 124 UNIX/Linux 47, 48, 49, 50
GeneratePDFReport.bat file 58 updating an MSC Enterprise Mvision 27
Global Properties 71 verifying 55
Global.properties file 65, 69, 71 Windows 39
parameters of 72 Installing MiKTeX 32
GrepDataList tag, changes to 102 Installing MSC Enterprise Mvision
GroupConfiguration.txt file 133 on UNIX 42
on Windows 39
preface to 16
H using superuser privileges (UNIX/
Linux) 42
Hardware
with mscsetup (UNIX/Linux) 45
requirements 17
with setup.exe 39
Windows XP 17
Installing Mvision databanks 60
Hardware requirements
Installing the Integrated Client
disk space 22
UNIX/Linux 56
memory 22
Installing the LDAP database 83
RAM 22
swap space 22
UNIX/Linux 19
HP kernel settings 23
228 INDEX
Integrated Client log

MscIntegratedClient.properties file 73 directory, contents of 36, 37
server-side configuration 73 files 81
setting default databank Categories 74
setting the GUI labels 74
SSL Encryption 103
Integrated Client Installation
M
Memory requirements
UNIX/Linux 56
core application 24
Windows 41
Disk space required 24
ior
for auxiliary databanks files used with
Enterprise Mvision 2001 25
for databanks 24
for UNIX 21
J for user sessions 25
jars virtual for databanks 24, 25
directory, contents of 36, 37 virtual memory 24
virtual memory for user sessions 25
Message Output
L customizing 81
Message output customization (MsgListener
LaTeX 18, 31
Interface) 81
downloading 31
Microsoft Visual C++ 6.0 18
downloading TeXLive 33
Migrating 2001 files to 2002 93
installing 31
Migrating 2002 files to 2004 92
installing pstricks 34
Migrating 2004 files to 2004r3.2 91
installing TeXLive on UNIX/Linux 33
Migrating 2004r3.2 files to 2006r1 files 90
MiKTeX 19
Migrating 2006r1 files to 2008r1 90
UNIX/Linux 31
Migrating V1.0 Files to 2001/2002 94
Windows (see MiKTeX) 31
MiKTeX 19, 31
LDAP 83
downloading 31
parameters 67
installing 32
Restricting access 83
msc daemon 190
Legend
position 66
creating default navigation views for 117
lib
example adding databank to 129
features and utilities 77
LIBPATH environment variable 41
integrated client on Windows 41
License file
obtaining license file for UNIX/Linux
editing on UNIX/Linux 193
189
editing on Windows XP 194
obtaining license file for Windows XP
forcing daemon to read 193
192
obtaining for UNIX/Linux 189
updating previous release 61
obtaining for Windows XP 192
MSC Mvision databanks 10
replacing on UNIX/Linux 193
MSC Mvision materials information system
replacing on Windows XP 194
products 10
LM_LICENSE_FILE variable 195
INDEX 229
MSC_LICENSE_FILE 192
MSC_SDM_IC_PROPERTIES_FILE
R
environment variable 41, 57 RAM 22
mscinfo 21 RC2 66
MscIntegratedClient.properties file 73 Replacing license file
mscsetup 45, 47 on UNIX/Linux 193
application options and prerequisites 52 on Windows XP 194
authorization form 52 Report Generation
custom 51 options 31
deselect 51 Report Generator 58
device selection 48 bat file 58
installation directory 49 configuring 58
selecting products 50 EmvHardcopies.properties file 58
standard install 51 formatted HTML 31
MsgListener Interface 81 PDF 31
XML 31
Required changes for Netscape Enterprise
N Server EMV 2002 101
Required configuration settings for iPlanet
Nodelock codes 194 Web Server 65
Required databank content modification 107
Required hardware & software
O configurations 21
Obtaining an MSC Enterprise Mvision Required software
license file java 20
UNIX/Linux 189 LaTeX 20
Windows XP 192 on the client (UNIX/Linux) 21
on the client (Windows XP) 19
on the server (UNIX/Linux) 20
P on the server (Windows XP) 18
web servers 20
Paging disk space 22 Requirements before installing MSC
Paths and server names, checking 190
PDF Report Generator Running Batch Builder 200
installing LaTeX 31
perl
Placing license file on server 189, 192
S
Preparing for installation 19 Scratch disk space 22
Previous release of MSC Enterprise Mvision, Security
updating 61 Login query 104
Ps-tricks 34 SSL Encryption of the Integrated Client
103
security
Q directory, contents of 36, 37
files 144
Query syntax example 209 Security Queries 104
230 INDEX
Select syntax example 211 221

SELECTEDROWS_0_VIEWS tag, changes to PDF report fails to display 222
102 report generator 221
Set the lmgrd daemon to start on reboot 191 server fails to start 216
Set up clients to access the floating license user connection to the EmvServer fails
192 217
Setting Chart Sizes 70 Windows fails to stop service 218
Setup and install Netscape Enterprise 35
Size of installation 19
Software requirements
for UNIX/Linux 20
U
Updating an MSC Enterprise Mvision
LaTeX 31
installation 27
MiKTeX 31
URL utilities 158
web servers 31
UserList.txt file 142
Windows XP 18
Using MSC Mvision 2002 Databanks 107
Spreadsheet syntax example 212
src
standard installation 51 V
Start the manager daemons 191 Version and log URLs 158
Starting VIEW_0 tag, changes to 102
EmvMonitor manually 80 Virtual memory required 24, 25
EmvMonitor on UNIX platforms 80 for databanks 24, 25
EmvMonitor with inittab 80
Swap 22
W
Web Server
T configuration 70
Tags WebServer.properties file 70
see EMV tags 102 web_server
Terms 107 directory, contents of 36
Troubleshooting WebServer.properties file 70
download to Excel 219
Downloading fails with SSL enabled 220
Emv Plot Macro 221
EmvMonitor fails to start (Windows) 216
X
XML output 31
EmvServer starts repeatedly from
Xvfb 64, 78
EmvMonitor 216
graphics fail to display in formatted
report 221
JSP pages fail on Windows 217
large curve image fails to display 217
logo fails to display in formatted report

MSC Enterprise Mvision

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

MSC Enterprise Mvision

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSC Enterprise Mvision

Uploaded by

Copyright:

Available Formats

MSC Enterprise Mvision

Installation and System Administration Guide

Publication Date: October 31, 2008

About This Guide ■ Introduction, 8

About This Guide

Organization of This Guide

■ MSC Mvision Materials Information System Products

MSC Mvision Materials Information System Products

MSC Mvision Software

MSC Mvision Databanks

Overview of MSC Mvision Products

Overview of MSC Mvision Product Line

For more information on the full line of MSC.Software

Before Beginning the Installation

Preparing for Installation on Windows XP

Required Software on the Server

It is recommended that you install all current service packs or patches

• BEA WebLogic Server 6.1 or higher

• . The system requirements for running the Sun Server include:

Required Software on the Client

Preparing for UNIX/Linux Installation

UNIX workstations have no special requirements. Refer to Required Hardware and

Required Software on the Server

It is recommended that you install all current service packs or patches

• We also recommend that you obtain and install a HTML/JavaScript editor

The pstricks files are found at:

Required Software on the Client

Memory Requirements for UNIX Workstations

Required Hardware and Software Configurations

mscinfo Utility Option Flags

mscinfo option: Use:

RAM, Swap, and Disk Space

Disk Space, Swap, and RAM Guidelines

Resource: Minimum: Standard:

HP-UX Kernel Settings

HP-UX Kernel Settings

Parameter: Description: Default: Recommended:

Parameters: Setting: Default:

General Memory Requirements

Memory Requirements for MSC Enterprise Mvision Core

Virtual Memory Required:

Memory Requirements for Databanks Used with MSC Enterprise

Virtual Memory Required:

Memory Requirements for Auxiliary Databank Files Used with MSC

Memory Requirements for User Sessions

Virtual Memory Required:

Updating an MSC Enterprise Mvision Installation

■ Updating a Previous Release of MSC Enterprise Mvision

Requirements Before Installing MSC Enterprise

Windows The Complete MiKTeX 2.5 http://miktex.org/

Installing MiKTeX 2.5 on Windows

4. Choose ‘Complete MiKTeX’ (about 400MB).

5. Select a mirror in you own country.

4. Choose to install the ‘Complete MiKTeX.’

5. Choose ‘Install for Anyone.’

Installing TeXLive 2007 on UNIX/Linux

2. Download the pstricks and pstricks-add packages or use the given

Alternatively add the binary path to

FLEXlm License System