cm 2011 1 sr2 installation guide

7/31/2019 Cm 2011 1 Sr2 Installation Guide

1/39

Corporate Modeler Suite 2011.1SR2

Installation and Configuration Guide


2/39

Corporate Modeler Suite 2011.1 SR2

ii


3/39

Contents

iii

Contents

About this Guide .............................................................................. 5Document audience...................................................................................... 5Document conventions ................................................................................. 5

Chapter 1................................................................................................. 6Installation overview ........................................................................ 6

Stand-alone installations............................................................................... 6Corporate Exchange installations ................................................................. 7Terminal Server installations ......................................................................... 7Virtual machine installations ......................................................................... 8

Chapter 2................................................................................................. 9Upgrading.......................................................................................... 9

Note for Portal users..................................................................................... 9Upgrade paths .............................................................................................. 9Important note on licensing ........................................................................... 9Upgrading from Corporate Modeler Suite 10.3 SR4, 10.3E, 2008.1, 2009.1,

2009.2, 2009.2 SR1, 2011.1 and 2011.1 SR1 ............................................. 10Corporate Modeler Suite 10.3 SR4 pre-upgrade procedure ......................... 11Backing up your data stand-alone version only ........................................ 12Restoring data stand-alone version only .................................................. 13

Chapter 3............................................................................................... 14Client installation ........................................................................... 14

System requirements .................................................................................. 14Before you begin ........................................................................................ 14Install Corporate Modeler Suite................................................................... 15Create a connection to Corporate Exchange ............................................... 15What next? ................................................................................................. 17

Chapter 4............................................................................................... 18Corporate Exchange SQL Server.............................................. 18

System requirements .................................................................................. 18Who should perform these actions? ............................................................ 18Before you begin ........................................................................................ 18Configuring SQL Server.............................................................................. 19


4/39

Contents

iv

Load models into Corporate Exchange ....................................................... 21What next? ................................................................................................. 21

Chapter 5............................................................................................... 22Corporate Exchange Oracle ...................................................... 22

System requirements .................................................................................. 22Who should perform these actions? ............................................................ 22Before you begin ........................................................................................ 22Configuring Oracle ..................................................................................... 23What next? ................................................................................................. 26

Chapter 6............................................................................................... 28Terminal Server .............................................................................. 28

System requirements .................................................................................. 28Who should perform these actions? ............................................................ 28Before you begin ........................................................................................ 28Configuring Terminal Server ....................................................................... 28

Chapter 7............................................................................................... 30Help and Support ........................................................................... 30

Web Desk .................................................................................................. 30Telephone and Email support ..................................................................... 30

Appendix A ........................................................................................... 32Configuring the Oracle client ....................................................... 32

Appendix B ........................................................................................... 33Load models into Corporate Exchange ...................................... 33

Appendix C ........................................................................................... 34Using SQL Server Authentication ................................................ 34

Enabling SQL Server Authentication ........................................................... 34Using SQL Server Authentication with Corporate Modeler Suite.................. 34

Appendix D ........................................................................................... 37VeriSign digital signatures ........................................................... 37

Problem details........................................................................................... 37How to resolve the problem ........................................................................ 37Enabling automatic VeriSign authentication ................................................ 37


5/39

About this Guide

5

About this Guide

This guide explains how to install Corporate Modeler Suite 2011.1 SR2 and set upand configure the various supported environments within which it can work.

It is recommended that you print this guide so that you can follow the instructionsmore easily when performing an installation.

Document audience

The Installation Guide is intended to be read by end users, system administrators anddatabase administrators who are concerned with setting up a Corporate ModelerSuite installation and related Corporate Exchange configuration.

Document conventions

Within this document variable names are presented in square brackets.

For example, [Username1] represents the name entered by the user to represent theusername they will use.

It is recommended that a list of these values is kept to ensure no mistakes are madeduring installation.

Note: Sometimes these values may need to be shared with other users, for example,when setting up a connection between a Corporate Modeler client and a CorporateExchange database.


6/39

Installation overview

6

Chapter 1


This chapter explains the different ways that you can work with Corporate ModelerSuite and how you set up the appropriate environment.

It is recommended that you read this chapter before trying to install CorporateModeler Suite so that you can determine the best system configuration to suit yourneeds.

There are four setup configurations for using Corporate Modeler Suite. They are:

1. Stand-aloneWhere you work independently on your local computer.

2. Corporate ExchangeWhere models are stored on a networked Corporate Exchange databasewhich can be accessed by many Corporate Modeler users.

3. Terminal ServerWhere users do not have Corporate Modeler Suite installed on their localcomputers, but use a copy by connecting to a Terminal Server which doeshave it installed.

4. Virtual machineWhere the software is installed on a virtual machine.

Note: Stand-alone and Corporate Exchange are not either/or configurations. A stand-alone user can at any time connect to a Corporate Exchange database, assumingone exists, and can switch between the two modes. Likewise, a Corporate Exchangeuser can choose to work in stand-alone mode, but this does assume that the clientsoftware was installed with the stand-alone option.

Stand-alone installations

If you want to use Corporate Modeler Suite completely independently of any network,shared database or Terminal Server, then you need a stand-alone setup.

This means that the software is installed on your local computer or laptop and you willbe able to use all its features and store your model data all on the one computer.

Note: If you choose to work locally in this way, you will always have the option ofconnecting to a shared network Corporate Exchange database whenever you want.

To install Corporate Modeler Suite so that you can work in stand-alone mode, readthe instructions in Chapter 3- Client installation, and ensure that during installationyou choose to work in network and local (stand-alone) modes.


7/39


7

Corporate Exchange installations

When numerous users within an organization use Corporate Modeler Suite, theyoften access models on a networked Corporate Exchange database. Depending onthe rights granted to each Corporate Modeler user, the models in the CorporateExchange database can be shared or private.

For this type of setup, each user has the Corporate Modeler Suite client softwareinstalled on their computers and has it configured to connect to a Microsoft SQLServer or Oracle database acting as a Corporate Exchange model store.

Figure 1. Client/server setup with Corporate Exchange

The Corporate Exchange database can be either Microsoft SQL Server 2005 or 2008,or Oracle 9i, 10g or 11.

Note: If any of the Corporate Exchange users additionally want the ability to workoffline, the client can be installed with a stand-alone database option. The stand-

alone option must be chosen at the time of installation as it cannot be addedsubsequently the only way to add the stand-alone database after installation is touninstall the software and install it again.

For information on installing the Corporate Modeler Suite client software, seeChapter3-Client installationand for information on configuring Corporate Exchange, seeeitherChapter 4-Corporate Exchange SQL ServerorChapter 5-CorporateExchange Oracle.

Terminal Server installations

One copy of the Corporate Modeler Suite client software must be installed perterminal server machine, each of which runs Microsoft Terminal Services and isaccessed by many users.

While Microsoft Terminal Services is the primary supported environment for this typeof installation, you can set up a similar environment using other remote accesstechnologies such as Citrix, as long as they are 100% compatible with MicrosoftTerminal Services.

For a Terminal Server installation, the client software cannot be installed with thestand-alone database option and must be configured to connect to a CorporateExchange database that is on a different computer to the Terminal Server/CorporateModeler client.


8/39


8

Figure 2. Terminal Server system configuration

For further information on installing Corporate Modeler Suite for use with a TerminalServer, please seeChapter 6-Terminal Server.

Virtual machine installations

Casewise does not formally test Corporate Modeler Suite in specific virtualenvironments. If you experience problems running Corporate Modeler Suite in avirtual environment, and these problems cannot be reproduced outside the virtualenvironment, Casewise requires that you seek support from your virtualizationvendor. Virtual environments must be configured as per the System Requirements for

the equivalent real machine.

Casewise does not support the investigation of performance issues for virtualenvironments that have not been configured in line with the System Requirements.

Apart from performance problems caused by inadequate virtual machine resources,Casewise is not currently aware of any problems running Corporate Modeler Suite onMicrosoft Virtual Server or VMware.


9/39

Upgrading

9

Chapter 2

Upgrading

If you want to upgrade from an earlier version of Corporate Modeler Suite, then youshould read this chapter carefully before installing any software.

If you are in any doubt about how to proceed with upgrading your copy of CorporateModeler Suite, please contact the Casewise Service Desk. SeeChapter 7- Help andSupportfor contact details.

In a multi-user environment where more than one client machine accesses a

Corporate Exchange repository you must upgrade all your clients.

Note for Portal users

If you use the Casewise Portal, then you may need to upgrade your Portal solution aswell. However, as new Corporate Modeler Suite releases tend to precede compatiblePortal releases, you should contact your Casewise account manager beforeupgrading to ensure a compatible Portal is available.

Upgrade paths

You can upgrade directly to Corporate Modeler Suite 2011.1 SR2 from versions10.3 SR4, 10.3E, 2008.1, 2009.1, 2009.2, 2009.2 SR1, 2011.1 and 2011.1 SR1.

If your Corporate Modeler version is earlier than 10.3 SR4 then you must firstlyupgrade to 10.3 SR4, and then upgrade to 2011.1 SR2. For information aboutupgrading to CM10.3 SR4 please refer to the installation guide for that version, which

is available on the Casewise website.

It is extremely important that you follow the upgrade instructionsexactly. If upgrading from10.3 SR4 pay particular attention to runningCM10Migrator, as specified in the section below entitledMulti-user

environments.

Important note on licensing

Corporate Modeler Suite 2009.1 included enhancements to the licensing functionalityover previous releases. Because of this, if you are upgrading from a pre-2009.1version, any existing licenses will not work with the new version.

If you upgrade without having the new licenses ready, you will not be able to usethe software until you have requested and received new licenses.


10/39

Upgrading

10

We therefore recommend that before you upgrade, you use your existing copy ofCorporate Modeler Suite to request new versions of all the licenses you require. Youcan use your existing License and Authorization IDs to do this.

When you request your new license, please make sure that you specify in thecomments or in the Email that the licenses are for the new 2011.1 SR2 version of

Corporate Modeler Suite.

Only once you have received your new licenses from Casewise should you proceedwith upgrading your software.

Upgrading from Corporate Modeler Suite 10.3SR4, 10.3E, 2008.1, 2009.1, 2009.2, 2009.2 SR1,2011.1 and 2011.1 SR1

Stand-alone users

Step 1 Back up your data

If you use a stand-alone database, we recommend that you backup your data as aprecaution. SeeBacking up your data stand-alone version onlybelow.

Step 2 Pre-upgrade procedure (Corporate Modeler Suite 10.3 SR4users only)

If you are upgrading from Corporate Modeler Suite 10.3 SR4, then you mustcomplete a specific procedure before you go any further. This procedure ensures that

the data in your repository is compatible with the new version.

SeeMulti-user environmentsbelow for full details and instructions. You must not goany further until you have completed this step.

Step 3 Install the new software on your machine

Follow the installation instructions detailed inChapter 3-Client installation.

Multi-user environments

Step 1 Prevent users from accessing the repository

Upgrading in a multi-user environment requires a change to the database schemawhich means anyone accessing the repository using any Casewise application willexperience problems.

It is therefore necessary to stop all users accessing the repository while the upgradetakes place.

Step 2 Back up your data

It is recommended that you back up your database before making any changes. Youshould use whatever backup procedure you are familiar with, or that is recommended

by your database provider.


11/39

Upgrading

11

Step 3 Pre-upgrade procedure (Corporate Modeler Suite 10.3 SR4users only)

If you are upgrading from Corporate Modeler Suite 10.3 SR4, then you mustcomplete a specific procedure before you go any further. This procedure ensures thatthe data in your repository is compatible with the new version.

SeeCorporate Modeler Suite 10.3 SR4 pre-upgrade procedurebelow for full detailsand instructions. You must not go any further until you have completed this step.

Step 4 Update the database schema

Updating the database schema involves manually executing a SQL command on thedatabase. You should only perform this task if you are confident doing so, otherwiseask a database administrator to help.

The command you need to execute is different depending on whether your databaseis Microsoft SQL Server or Oracle.

The database you need to execute the command against is probably titledCorporateModeler10, unless it was named differently to the suggested name.

For Microsoft SQL Server

If your database is running on Microsoft SQL Server 2005 or 2008, execute thefollowing command in SQL Management Studio:

ALTER TABLE CW_OBJECT_TYPE ADD OT_CW_RESTRICTIONS NVARCHAR(MAX)COLLATE Latin1_General_BIN NULL

For Oracle

If your database is running on Oracle, use SQL PLUS to log on to the database asCWSCHEMAOWNER and execute the following command:

ALTER TABLE

CW_OBJECT_TYPE

ADD

OT_CW_RESTRICTIONS nclob NULL;

Step 5 - Install the new software on all client machines

Once you have updated the database schema, you should update all client softwareinstalled on users machines. Follow the installation instructions detailed inChapter 3-Client installation. Once you have run and completed the setup, you can ignore theother instructions as your connection details to your Corporate Exchange repositorywill be maintained.

Corporate Modeler Suite 10.3 SR4 pre-upgradeprocedure

If you are upgrading from Corporate Modeler Suite 10.3 SR4, you must perform thefollowing task before attempting to upgrade:


12/39

Upgrading

12

Run CM10Migrator to ensure all your data is compatible with CorporateModeler 2009.2

To do this:

i. Navigate to your Casewise Bin directory, usually C:\Program

Files\Casewise\CM10\BIN

ii. Run CM10Migrator.exe

Follow the wizard prompts.

CM10Migrator produces a log file called Migration.txt in the folder: MyDocuments\Casewise

Although it is advised that you take a manual backup of your stand-alone databasebefore upgrading from either CM10.3 SR4 or CM10.3E, CM10Migrator creates abackup copy of the database anyway. The backup file is called CMDB.bkp and isstored in the folder: C:\Program Files\Microsoft SQL

Server\MSSQL.1\MSSQL\Backup. It can be up to 2Gb in size, and can also berestored using the procedure detailed below. Should you not wish to keep theautomatic backup file, you can delete it.

Backing up your data stand-alone version only

This section is only relevant if you are upgrading a stand-alone version of CorporateModeler Suite.

Note: the user running the SQL Server service must have write access to the chosenbackup folder. To check the properties of the service, select Start > Control Panel >

Administration Tools > Services, highlight SQL Server (MSSQLSERVER) and goto Action > Properties (or right-click and select Properties). The Log On tab showswhich user the service logs on as usually Local System.

To backup your stand-alone data:

1. Open a command prompt

2. In the command prompt window enter the following code exactly as it isshown below, and press Return:

OSQL -E -S %COMPUTERNAME%\CASEWISE

3. Enter the following code and press Return after each line:

Backup database CorporateModeler10 TO DISK =\.bak2> Go

Note: is the location where you want to save your backup file, and is the name of the file. For example, could beC:\temp while could be MyDatabase, resulting in the following\.bak: C:\temp\MyDatabase.bak

When the backup has finished the message: BACKUP DATABASEsuccessfully processed is displayed.

4. Type Exit at the prompt


13/39

Upgrading

13

Restoring data stand-alone version only

This section is only relevant to stand-alone versions and obviously requires that youhave previously backed up the data.

To restore data in a stand-alone database:

1. Open a command prompt

2. In the command prompt window enter the following code exactly as it isshown below, and press Return:

OSQL -E -S %COMPUTERNAME%\CASEWISE

3. If the Casewise database already exists in MSDE/SQL Server Express, enterthe following code:

1> Restore database CorporateModeler10 from disk =

\.bak with replace2> Go

If the Casewise database does not exist, enter the following code to createthe database and restore your data

Create database CorporateModeler10;2> Go3> Restore database CorporateModeler10 from disk =\.bak with replace4> Go

Note: is the location where you saved your backup file, and

is the name of the file.


14/39

Client installation

14

Chapter 3

Client installation

This chapter describes how to install the Corporate Modeler Suite client software.You can access the setup program by downloading from the Casewise website, or byusing the Casewise DVD. Please read theBefore you beginsection before installingthe software.

System requirements

Please refer to the system requirements documents available on the Casewisewebsite for further details.

Before you begin

If you are installing Corporate Modeler Suite as a client to connect to a CorporateExchange database, it is recommended that you set up Corporate Exchange first.

You must have Administration rights on your computer to install Corporate ModelerSuite. Please see your system administrator for assistance.

Get the Corporate Modeler Suite DVD or download the setupfile

Get your Casewise DVD ready, or download the latest version of the software fromthe Casewise website.

If you are using the download file, please note there are different versions ofthe software for 32-bit and 64-bit versions of Windows, so please ensureyou download the correct version.

32-bit version: CMSetup****-*-***-x86.exe64-bit version: CMSetup****-*-***-x64.exe

Upgrade to Windows Installer 4.5

If you plan to install the stand-alone database, you must have Windows Installer 4.5installed. This Windows component is not upgraded through normal WindowsUpdates, so needs to be installed manually.

To download the file, go to:http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4


15/39

Client installation

15

Install Corporate Modeler Suite

It is important that you follow the steps in this installation guide in order if you want toavoid any problems installing the software.

To install Corporate Modeler Suite:

1. If you have the Corporate Modeler Suite DVD, insert the disc into yourcomputer and the setup program should run automatically.

If you have the download file, double-click it to launch the setup program.

There are different versions of the download file for 32-bit and 64-bit versions of Windows, so please ensure you use the correctversion.

32-bit version: CMSetup****-*-***-x86.exe64-bit version: CMSetup****-*-***-x64.exe

2. Follow the on-screen prompts in the setup wizard.

Note: If you want to be able to work in stand-alone mode, be sure to makethe appropriate selection during setup. The ability to connect to a CorporateExchange database is always available, assuming you have one to connectto. For an explanation of the different working modes, see Chapter 1 -Installation overview.

If you are upgrading, you do not need to read on any further than this point.

Create a connection to Corporate ExchangeThis section is only relevant to users who want to connect to an existing CorporateExchange database. If you are only using Corporate Modeler Suite in stand-alonemode, please go straight to theWhat next?section.

Note: If you want to connect to Corporate Exchange Oracle, please ensure youhave followed the instructions inAppendix A-Configuring the Oracle clientbeforecontinuing.

To connect to your Corporate Exchange server:

1. Start any program in the Corporate Modeler Suite.

The Corporate Modeler Suite Logondialog opens

Note: If you logon automatically and therefore do not normally see the logondialog, you must hold down the Shift key while starting the program bylaunching it from the Start menu.

2. From the Database section, click Edit.

The Database Connectiondialog opens.

3. Click Add and select one of the following:

SQL Server


16/39

Client installation

16

Oracle Database.

The Configure Databasedialog opens.

Notes:

IfFor this user is selected, the connection is only available for thespecific Windows user who created it.

IfFor this computer is selected, the connection is available toanyone who uses the computer.

To access the option For this computer on Windows Vista, youmust launch any program in the Corporate Modeler Suite by right-clicking on its shortcut and selecting the option Run asadministrator.

If you do not select the option Run as administrator then only theoption For this user is available.

4. Complete all fields in the Configure Databasedialog as appropriate:

For Corporate Exchange SQL Server:

Connection name - This is the name that you assign to thisconnection. It will be shown in the database drop-down list that usersof this machine will see when they log on, so it should be a clearname describing the content stored on this copy of CorporateExchange.

Server name - This is the name of your SQL Server.

Database name [database_name]

Instance name and Port number are not required by default,however they may be necessary depending on the particularconfiguration of your SQL Server. See your SQL Administrator for thedetails.

User name, Password, and Confirm password are only required ifyour SQL Server is configured to use SQL Server Authentication.See your SQL Administrator for the details.

For Corporate Exchange Oracle:

Connection name - This is the name that you assign to thisconnection. It will be shown in the database drop-down list that usersof this machine will see when they log on, so it should be a clearname describing the content stored on this copy of CorporateExchange.

Service - [name].

User name - CASEWISE.

Password / Confirm Password - [Connect password].

Oracle 10g+ users only:Server name - This is the physicalComputer name or Server name defining the machine on which the


17/39

Client installation

17

server resides (this is not required if you are using an Oracle servicename resolution).

5. Click OK.

The database connection is checked and created.

Note: Even if the test connection made at this point is unsuccessful, thedetails will still be saved and you will still be able to select it in the logondialog.

What next?

Now you have installed Corporate Modeler Suite, and connected to the CorporateExchange database if you are using one, you can proceed to use the software asrequired.

To run the software, click the icon on your desktop, or go to:

Start > All Programs > Casewise Corporate Modeler Suite > Start Here .

When you start one of the Corporate Modeler Suite programs, you are prompted toselect a database and log on to it.

Log on to Corporate Modeler

Stand-alone user

If you are using the stand-alone database, you should log on with the Username

ADMIN and leave the password blank. You can add a password after you havelogged on if you want to make your models more secure.

Corporate Exchange user

If you are the first user to log on in a multi-user environment, and you will be themodel administrator, you should log on with the Username ADMIN and leave th epassword field blank.

It is the Corporate Modeler Administrators responsibility to set up the other CorporateModeler Users, including assigning Usernames and Passwords.

We recommend that you make the Administration account more secure by adding apassword of your choice.

The Administrator should inform the other Corporate Modeler Users of their logondetails so they can successfully log on to Corporate Modeler once they have installedthe client software.

If you are a user in a multi-user environment, connected to Corporate Exchange, seeyour Corporate Modeler Administrator for your logon details.


18/39

Corporate Exchange SQL Server

18

Chapter 4


This chapter provides instructions for users who wish to set up a new copy ofCorporate Exchange - SQL Server.

The only versions of SQL Server which can be used with Corporate Modeler Suiteare SQL Server 2005 and SQL Server 2008 (all but Express edition, which is only forthe stand-alone database).

This guide does not provide instructions on installing Microsoft SQL Server itself.

Please refer to the product documentation provided by Microsoft.

Note: There is no additional software to install on the SQL Server. The instructions inthis chapter are to configure the database to be ready for use with Corporate ModelerSuite.

System requirements


Who should perform these actions?

The majority of the tasks in this chapter should be performed by a SQL ServerDatabase Administrator (DBA), however there are some tasks for a nominatedCorporate Modeler user.

Before you begin

It is a prerequisite of this guide that you have already installed Microsoft SQL Serveritself. SQL Server should be on a different computer to the one which you will install

the Corporate Modeler Suite client software on.

Access the SQL script files

The SQL script files you need for the installation are available from the Casewisewebsite and the CorporateExchange\MSSQL\ directory on the DVD. The websitefiles are zipped in a file titled:

MSSQLCreateScripts.zip

The actual scripts, and the ones on the DVD are:

CreateCasewiseRWRole.sql


19/39


19

CreateMSSQLCopyModelProcedure.sql

CreateMSSQLDeleteModelProcedure.sql

CreateMSSQLSchema.sql

GrantAccessToSchemaForCasewiseRWRole.sql

GetNextId.sql

Configuring SQL Server

The instructions for configuring the SQL Server database to work as a CorporateExchange model store are broken down into task-based sections.

Create a new database

From SQL Server Management Studio:

1. In the left-hand pane, select the SQL Server that you want to use.

2. Right-click Databases and select New Database.

3. On the New Databasedialog, enter:

Database name: [database_name]

4. Click Options in the Select a page panel on the left of the dialog

5. In the Collation drop-down box select Latin1_General_CI_AS .

Note: if you know that the default setting () isLatin1_General_CI_AS then there is no need to change the Collationsetting

6. Click OK.

Run SQL scripts

Running the SQL scripts creates the schema and role, and grants access to the

tables.


1. Go to File > Open

2. Open each of the following SQL script files in turn:

CreateMSSQLSchema.sql

CreateMSSQLCopyModelProcedure.sql

CreateMSSQLDeleteModelProcedure.sql

GetNextId.sql


20/39


20

CreateCasewiseRWRole.sql.

GrantAccessToSchemaForCasewiseRWRole.sql.

3. For each file, select the database you just created in the SQL Editortoolbar

4. Run each file by clicking the Execute button:

Create database user

The instructions for creating a user here describe how to do so using WindowsAuthentication. We recommend using Windows Authentication for your databaseuser. If however you prefer to use SQL Server Authentication, please seeAppendix C-Using SQL Server Authentication.


1. In the left-hand pane, expand the SQL Server instance.

2. Expand Security.

3. Right-click Logins and select New Login.

The Login Newdialog is displayed.

4. In the Login name field, enter a Windows User name, or Windows UserGroup name.

If you want to enter a User Group, or search for a User or User Group, toenable Groups:

i. Click the Search button.

The Select User or Groupdialog is displayed.

ii. Click the Object Type button.

The Object Typesdialog is displayed.

iii. Select Groups

iv. Click OK.

To search for a User or User Group:

i. Enter a fully-qualified User name or User Group name

ii. Click Check Names.

iii. If the name resolves, click OK.

The Select User or Groupdialog closes.

5. In the Login Newdialog, click OK.

6. In the left-hand pane, expand your new database node.

7. Expand Security.


21/39


21

8. Right-click Users and select New User.

The Database User Newdialog is displayed.

9. For the User name, enter the name of the new user: [db_username].

10. Click the Browse () button next to the Login name field.

The Select Logindialog opens.

11. Click Browse.

The Browse for Objectsdialog opens.

12. Select the User or User Group to give access to the database to (the one justgranted when creating the login).

13. Click OK.

14. Click OK.

15. On the Database User New dialog, select CasewiseRW in the OwnedSchemas and Role Members sections.

16. Click OK.

Your user is created.

Load models into Corporate Exchange

Install a single copy of Corporate Modeler on a client machine a different computerto the Corporate Exchange server.

Create a connection from the Corporate Modeler client to your Corporate ExchangeSQL Server.

Load Corporate Modeler models into the database seeAppendix B-Load modelsinto Corporate Exchange.

The models are now loaded into your Corporate Exchange SQL Server databaseand are ready to be used.

What next?

Now you have configured Corporate Exchange SQL Server and loaded the modeldata, the server is ready to be used.

Before users install their client software and log on to the Corporate Exchange server,it is advised that one nominated key user, a Corporate Modeler Administrator, shouldlog on to and create the User accounts for the other users.

The Corporate Modeler Administrator can set permissions and access rights on themodels and it is therefore recommended they change the default logon details for theAdministration account.


22/39

Corporate Exchange Oracle

22

Chapter 5


This document provides instructions for users who wish to set up a new copy ofCorporate Exchange Oracle using Oracle 9i or 10g.

If you want to run Corporate Exchange on Oracle 11, please contact the CasewiseService Desk for assistance. SeeChapter 7-Help and Support.

This guide does not provide instructions on installing Oracle itself. For information oninstalling Oracle, please refer to the product documentation provided by Oracle.

Note: There is no additional software to install on the Oracle server. The instructionsin this chapter are to configure the database to be used with Corporate ModelerSuite.

System requirements


Who should perform these actions?The majority of the tasks in this chapter should be performed by an Oracle DatabaseAdministrator (DBA), however there are some tasks for a nominated CorporateModeler user.

Before you begin

It is a prerequisite of this guide that you have already installed Oracle itself. Oracleshould be on a different computer to the one which you will install the CorporateModeler Suite client software on.

Access the SQL script files

The SQL script files you need for the installation are available from the Casewisewebsite and the CorporateExchange\Oracle\9 or CorporateExchange\Oracle\10directories on the DVD. The website files are zipped in a file titled:

Oracle10CreateScripts.zip or Oracle9CreateScripts.zip

The actual scripts, and the ones on the DVD are:

CreateOracle10Schema.sql or CreateOracle9Schema.sql

CreateOracleCopyModelProcedure.sql


23/39


23

CreateOracleDeleteModelProcedure.sql

CleanDb.sql

CreatePrivateSynonymsForCasewiseTables.sql

GetNextId.sql

GrantAccessToSchemaForCasewise.sql

Configuring Oracle

The instructions for configuring an Oracle database to work as a Corporate Exchangemodel store are broken down into tasks. The table below shows which user must belogged on to perform each task.

These instructions are for both Oracle 9i and 10g. Any differences are highlighted.

Note: Corporate Modeler requires its own dedicated Oracle instance.

Note on running SQL scripts: You must use SQL Plus to run all SQL scripts toavoid lines being truncated by SQL Plus Worksheet.

1. User: DBA

Create Oracleinstance

Global Database Name: [name]

Character Set:AL32UTF8

National Character Set:AL16UTF16

We advise you turn off all Standard DatabaseFeatures and set Database Connection Optionsto Dedicated Server Mode

2. User: DBA


24/39


24

Create users User 1

Name: CWSCHEMAOWNER

Password: [dba_password]

Rights:

create any synonym

create procedure

create session

create table

create tablespace

resource

User 2

Name: CASEWISE

Password: [cw_password]

Rights:

create session

3. User: DBA

Create CASEWISEtablespace

Name: CASEWISE

File size: 500 MB

Extent Management:

Locally Managed

Automatic Allocation

Segment space management: Automaticallyextend (AUTOEXTEND)

4. User: DBA

CreateCASEWISEIDXtablespace

Name: CASEWISEIDX

File size: 500 MB

Extent Management:

Locally Managed

Automatic Allocation


5. User: DBA


25/39


25

CreateCASEWISELOBJtablespace

Name: CASEWISELOBJ

File size: 500 MB

Storage:

Uniform Allocation

5 MB


6. User: DBA

CreateCASEWISELOBJIDXtablespace

Name: CASEWISELOBJIDX

File size: 500MB

Storage:

Uniform Allocation

5 MB


7. User: CWSCHEMAOWNER

Run SQL scripts Run:

CreateOracle9Schema.sql orCreateOracle10Schema.sq

CreateOracleCopyModelProcedure.sql

CreateOracleDeleteModelProcedure.sql

GetNextId.sql

CreatePrivateSynonymsForCasewiseTables.sql

GrantAccessToSchemaForCasewise.sql

8. User: DBA

Clean up Run:

CleanDb.sql

9. User: DBA


26/39


26

Tune Oracle settings The settings below are for 10 concurrent users.

Enter and execute the following:

For Oracle 9

alter system set sga_max_size=6400m

scope=spfile;

This assumes 80% of a 8 GB memory

alter system set sort_area_size=507904scope=spfile;

alter system set db_cache_size=350mscope=spfile;

alter system set pga_aggregate_target=80mscope=spfile;

alter system set optimizer_mode=choosescope=spfile;

For Oracle 10

alter system set sga_target=800m scope=spfile;

alter system set sort_area_size=507904scope=spfile;

alter system set pga_aggregate_target=80mscope=spfile;

Once completed, restart Oracle.

10. User: Corporate Modeler user

Load model data SeeAppendix B-Load models into CorporateExchange this task to be performed by a CorporateModeler client user on a client machine.

11. User: CWSCHEMAOWNER

Completeconfiguration

Run the following SQL script:

executedbms_stats.gather_schema_stats(ownname=>CWSCHEMAOWNER ,cascade=> TRUE);

What next?

Now you have configured Corporate Exchange Oracle and loaded the model data,the server is ready to be used.

Before users install their client software and log on to the Corporate Exchange server,it is advised that one nominated key user, a Corporate Modeler Administrator, shouldlog on to and create the User accounts for the other users.

The Corporate Modeler Administrator can set permissions and access rights on themodels and it is therefore recommended they change the default logon details for theAdministration account.


27/39


27

Oracle with Terminal Server or Citrix

Installations that use a Terminal Server or Citrix server in combination with an Oraclerepository will experience poor performance for a number of architectural reasons notpresent when using a SQL Server repository. In particular, poor performance isexperienced when a users home drive is located on a file system other than the

Terminal Servers or Citrix servers own file system.

To avoid this performance issue, it is advisable to locate your users home drives onthe Terminal Server or Citrix server.


28/39

Terminal Server

28

Chapter 6

Terminal Server

A Terminal Server installation involves one copy of the Corporate Modeler Suite clientsoftware being installed on a machine with Microsoft Terminal Services enabled,which is accessed by many users.

Casewise supports installations that match the environment described in this chapter,however you can adapt this setup and use it with other remote access technologies,such as Citrix, as long as they are 100% compatible with Microsoft Terminal Services.

System requirements


Who should perform these actions?

The majority of the tasks in this chapter should be performed by a SystemAdministrator, however there are some tasks for a nominated Corporate Modeleruser.

Before you begin

It is a prerequisite that you have already set up your Terminal Server and installed allpre-requisite software.

Configuring Terminal Server

Note: You cannot install the stand-alone database. Instead configure Corporate

Modeler to connect to your Corporate Exchange database.

To install Corporate Modeler Suite on Terminal Server:

1. Set up and configure a Corporate Exchange server on a different machine tothe Terminal Server seeChapter 4-Corporate Exchange SQL ServerorChapter 5-Corporate Exchange Oraclefor further information.

2. Set the Terminal Server machine to Install mode.

3. Install the Corporate Modeler client software on the Terminal Server seeChapter 3-Client installation.


29/39

Terminal Server

29

Once you have installed Corporate Modeler Suite, you can treat it as any other clientinstallation. See theWhat next?section inChapter 3-Client installationfor moreinformation about what to do now.

Note: if you use Terminal Server or Citrix in combination with an Oracle repository,seeOracle with Terminal Server or Citrix


30/39

30

Chapter 7

Help and Support

Web Desk

You can submit a request for assistance and search our knowledge base on our webdesk support system:

http://www.casewise.com/support/

Telephone and Email support

Casewise provides telephone and Email support services to registered users whohave paid their annual maintenance charge. The service is available during normaloffice hours.

When you contact Service Desk for help, please ensure that you include the followinginformation in your email, or have it at hand if you are telephoning:

Your name and organization name

Your Auth ID. For client licenses, this is the code you entered when you

registered for a license. For server licenses, please obtain the Auth ID fromyour system manager

The version number of Corporate Modeler Suite you are using

Your Operating System

Any error messages you have encountered, or the precise steps that causedthe problem

For Corporate Publisher HTML problems, your Internet browsers name andversion number.

For Europe, Asia and Australasia

For technical queries, contact the Casewise Service Desk on: +44 (0)1923 830 333

Note:

if calling from Germany, you can instead call 0800-CASEWISE (0800-22739473)

if calling from France, you can instead call 01 53 43 93 92

For general and business queries, contact your Casewise account manager on: +44(0)1923 830 300


31/39

Help and Support

31

Email: [email protected]

For USA, North and South America

For technical queries, contact the Casewise Service Desk on: +1 856-380-1400

For general and business queries, contact your Casewise account manager on: +1856-380-1400

Email: [email protected]


32/39

Appendix A - Configuring the Oracle client

32

Appendix A

Configuring the Oracle client

If you are using version 9 of the Oracle client software, you must configure it toconnect to Corporate Exchange Oracle, before you try to create a connection inCorporate Modeler.

To connect the Oracle client to Corporate Exchange Oracle:

1. Open the Oracle Net Configuration Assistant.

2. On the Welcomepage, click Local Net Service Name Configuration.

3. On the Net Service Name Configurationpage, click Add.

4. On the Net Service Name Configuration, Service Namepage, enter[name].

5. On the Net Service Name Configuration, Select Protocolspage, select TCP.

6. On the Net Service Name Configuration, TCP/IP Protocolspage, enter[hostname].

Where [hostname] is the physical computer name of the machine hostingCorporate Exchange Oracle.

7. Test the connection using the CASEWISE users logon details.

8. On the Net Service Name Configuration, Net Service Namepage, enter[name].

9. Complete the wizard and click Finish.


33/39

Appendix B - Load models into Corporate Exchange

33

Appendix B

Load models into Corporate Exchange

The tasks in this section should be performed on a client machine by a CorporateModeler user.

If you have not already done so, please install a Corporate Modeler Suite client andcreate a connection to your Corporate Exchange database. SeeChapter 3, sectionsClient installationandCreate a connection to Corporate Exchangefor instructions onthese tasks.

For users to be able to use Corporate Modeler, you must load all the modelsdelivered with the Corporate Modeler client into the Corporate Exchange database.

From the Corporate Modeler client machine:

1. In Windows Explorer, browse to the file: LoadCasewiseModels.exe

The file can be found in the Casewise Bin directory, (usually C:\ProgramFiles\Casewise\CM10\Bin\)

2. Run the program

The wizard starts.

3. Progress through the wizard, making sure to select the following options:

The target database is your new Corporate Exchange database

In response to the question asking if you are upgrading, reply No

4. When the wizard completes, click Finish.

The models are now loaded into your Corporate Exchange database and areready to be used.


34/39

Appendix C - Using SQL Server Authentication

34

Appendix C

Using SQL Server Authentication

While it is recommended that you use Windows Authentication when setting up useraccess to your Corporate Exchange SQL Server data, you can use SQL ServerAuthentication if you prefer.

Enabling SQL Server Authentication

SQL Server Authentication is disabled by default in SQL Server 2005 and 2008.

To enable SQL Server Authentication:

1. Run SQL Server Management Studio

2. Connect to the server which hosts your Corporate Exchange database usingWindows Authentication

3. In the left-hand pane, right-click the SQL Server hosting your database

4. From the right-click menu, select Properties

The Server Propertiesdialog opens

5. In the Select a page section on the left of the dialog, select Security

The security settings are displayed

6. UnderServer authentication, select SQL Server and WindowsAuthentication mode

7. Click OK

For further information on using setting your server up to use SQL ServerAuthentication, please refer to the Microsoft documentation.

Using SQL Server Authentication with CorporateModeler Suite

To use SQL Server Authentication with Corporate Modeler Suite you must first createa new SQL Login and then specify that login in the database connection used by theCorporate Modeler Suite client software.

Create a new SQL Login using SQL Server Authentication

To create a new SQL Login:


35/39


35

1. In the left-hand pane of SQL Server Management Studio, expand the SQLServer instance.

2. Expand Security.

3. Right-click Logins and select New Login.

The Login Newdialog is displayed.

4. In the Login name field, enter a login name: [login_name].

5. Select SQL Server Authentication.

6. Enter a Password for the new login: [password]

7. Confirm the password.

8. Deselect the Enforce password expiration.

9. Click OK.

The Login Newdialog closes.

10. In the left-hand pane, expand Databases.

11. Expand Security.

12. Right-click Users and select New User.

The Database User Newdialog is displayed.

13. For the User name, enter the name of the new user: [db_username]

Note: To make things easier, we recommend using the same name here asyou entered before for [login_name].

14. Click the Browse () button next to the Login name field.

The Select Logindialog opens.

15. Click Browse.

The Browse for Objectsdialog opens.

16. Select the new Login user you just created: [login_name].

17. Click OK.

18. Click OK.

19. On the Database User New dialog, select CasewiseRW in the OwnedSchemas and Role Members sections.

20. Click OK.

Your user is created.


36/39


36

Specify the SQL Login in the database connection

Once you have enabled SQL Server Authentication and created your new Login, youmust then specify the username and password used for the Login in the databaseconnection details used by your Corporate Modeler Suite client or clients.

You can do this by editing the details of an existing connection, or by creating a newconnection.

To access the Database Connection dialog for Corporate Modeler Suite, run any ofthe Corporate Modeler Suite applications and in the Database section of the Logondialog, click Edit.

Use the Help button on the dialog to find out how to create new connections or editexisting connections.


37/39

Appendix D - VeriSign digital signatures

37

Appendix D

VeriSign digital signatures

Casewise software uses VeriSign to reassure you of the authenticity of our software.Automatic VeriSign authentication normally executes each time you run any of theCorporate Modeler Suite .NET applications. However, due to an issue with Microsoft.NET 2.0 which results in long loading times for some applications, we have turnedoff this automatic authentication by default.

This Appendix explains the issues behind the problem and informs you how you canresolve the problem, as well as how to enable automatic VeriSign authentication on

application startup.

Problem details

The following Corporate Modeler applications are affected by the problem:

Start Here page (bwindw.exe)

Corporate Modeler (CorporateModeler.exe)

Automodeler (Automodeler.exe)

Object Explorer (ObjectExplorer.exe)

For full details on the causes of the issue, please see:http://support.microsoft.com/kb/936707

How to resolve the problem

You can resolve the problem by downloading and installing the .NET Framework 2.0Service Pack 1:

http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en

Enabling automatic VeriSign authentication

If you want to enable automatic VeriSign authentication then follow the procedurebelow:

1. On the client machine, navigate to your Casewise Bin directory, usuallyC:\Program Files\Casewise\CM10\BIN

2. Open bwindw.exe.config in a text editor:
http://support.microsoft.com/kb/936707http://support.microsoft.com/kb/936707http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=enhttp://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=enhttp://support.microsoft.com/kb/936707


38/39

Appendix D - VeriSign digital signatures

38

3. In the section of code, locate the followingline:

4. Change the code to:

5. Repeat steps 2 to 4 for the following file:

CorporateModeler.exe.config

Automodeler.exe.config

ObjectExplorer.exe.config


39/39

Notes: