DB Installation Manual Wise v5.6 v1.0

Installation Manual

Wise Package Studio v5.16

Infrastructure Integration

IN FAVOUR OF: Getronics Centric MK

CONTACT: Paul O' Connor

DOCUMENT NAME: document.doc

VERSION: 1.0

STATUS: Final

AUTHOR(S): Getronics Centric MK

Statutory Seat Amsterdam

Trade Register 34115845

Getronics Centric MK

Foxhunter Drive

Linford Wood East

Milton Keynes

MK14 6GE

Tel:01908 573758

Fax:01908 573749

www.getronics.com

Table of Contents

Management Summary

This manual describes the installation method for the Wise Package Studio v5.6 environment, so that all installations are conducted in the same way, for all customers.

Included in this manual are the system requirements for the environment, the installation of the SQL Server, the Wise Package Studio Server, Wise Package Studio on packaging machine and the Wise Package Studio Client. Finally the configuration of the package environment it described.

document.doc

Version 1.0 • Final

© Getronics Centric MK

2/63

Table of Contents

Version- and Distribution Page

Version

After this document has reached the “final” status (as of version 1.0), this paragraph will list the changes as compared to previous versions.

Small changes, for example; typographic errors and small textual changes, are not listed individually; they will be compiled under “Textual changes and corrections”.

New final versions of a document do not necessarily include all additions of previous final versions.

Version Date Author(s) Changes

1.0 June, 06 2005 P. O’ Connor

1.1 Sept, 29 2005 P. O’ Connor

Last checked by Date

Distribution

Amount Receivers Location

document.doc



3/63

Table of Contents

All rights reserved.

Contents of this publication may not be duplicated and/or made public in any way nor by any medium including; printing, photocopying and microfilm or otherwise, without the prior written permission of Getronics Centric MK.

This injunction also applies to all future adaptation of the publication in full and/or part.

Duplication and distribution of this document is permitted by Getronics Centric MK, explicitly for internal use by the principal.

document.doc



4/63

Table of Contents

Table of Contents

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

1.1 Before the installation starts.................................................................................61.2 Hardware..............................................................................................................61.2.1 Harddisk Space SQL Databases............................................................................61.2.2 Harddisk Space Wise Share Point..........................................................................61.2.3 Memory.................................................................................................................71.3 Software...............................................................................................................81.3.1 SQL Server............................................................................................................81.3.2 Operating System.................................................................................................8

2 Installing SQL Server Client Tools.........................................................................9

3 Installation of Wise Package Studio v5.6 on Packaging Machine.........................15

3.1 Wise Package Studio v5.6...................................................................................153.2 Synchronise Merge Modules on local machine....................................................25

4 Wise Package Studio v5.6 Client.........................................................................26

4.1 Requirements.....................................................................................................264.2 Installing the Client.............................................................................................26

5 Configuration Wise Package Studio v5.6.............................................................34

5.1 Initial Workbench Setup......................................................................................345.1.2 Define SetupCapture Standards..........................................................................355.1.3 Capture Standard Operating Environment..........................................................425.1.4 Customize Windows Installer Template...............................................................465.1.5 Customize Windows Installer Options.................................................................475.1.6 Customize WiseScript Template..........................................................................495.1.7 Define ConflictManager Settings.........................................................................515.2 Configuration Tools Tab......................................................................................555.3 Preferences.........................................................................................................575.4 Process Templates Setup....................................................................................595.5 Project Setup......................................................................................................69

Annex 1 Configure Wise Package Studio for SQL Server Authentication...........................81

A 1.1 Creating the SQL Server User.............................................................................81A 1.2 Modifying the System DSN..................................................................................87A 1.3 Registry Setup....................................................................................................90

document.doc



5/63

Configuration Wise Package Studio v5.6

1 System Requirements

For the installation of Wise Package Studio there are several specific requirements. Some of these requirements depend on the amount of applications that need to be repackaged.

1.1 Before the installation starts

Before the installation of Wise Package Studio can start, the following things must be already done:

There is a server with enough harddisk space for Wise Package Studio; There is a server with enough internal memory for Wise Package Studio;

The Operating System is already installed on the Wise Package Studio server;

All license codes for Wise Package Studio v5.1 are available.

A complete packaging environment is installed, with:

o Domain controllers;

o An image for the clients;

o All applicable policies;

o File- and/or printservers;

o A server with the distribution tool installed;

1.2 Hardware

1.2.1 Harddisk Space SQL Databases

The application depends on a SQL Server that is installed. This installation can reside on the Wise Package Studio server, or it is possible to reside the databases on a server that already has SQL Server installed. In the database, 2 to 4 MB of storage per each application is sufficient. Only string information, such as registry keys and values, and file names are stored in the database. This would need to be multiplied by the number of expected applications.

document.doc



6/63


For Example, if there were 500 applications, a 2 GB drive would actually be sufficient for SQL.

1.2.2 Harddisk Space Wise Share Point

Depending on the size of each application, it is possible that some will require approx 1/2 GB, for such large applications as MS-Office, MS-Visio, Visual Studio editions, Oracle, and so on. Some applications will require 10 or 20 MB, such as WinZip or Adobe Reader. Assume an image of the manufacturer’s distribution method (such as CD) will be duplicated on the sharepoint’s drive plus the .MSI file that will be created from repackaging.

If the installation source is also copied to the sharepoint directory this increases the size needed.

1.2.3 Memory

Wise Package Studio doesn’t need that much memory to run, but the SQL Server and databases do. As much as 1,5 GB of memory can be in use by the SQL Server.

document.doc



7/63


1.3 Software

1.3.1 SQL Server

The data that needs to be stored in databases can be stored in:

SQL Server;

MS Access Database.

Because there is al lot of data imported in the databases, it is strongly recommended to use SQL Server, instead of the Microsoft Data Engine (MSDE) or MS Access.

The versions that can be used are:

SQL Server 2000 Personal Edition; SQL Server 2000 Enterprise Edition;

And later versions.

1.3.2 Operating System

Because SQL Server is strongly recommended, the operating system must be one from the server platform. SQL Server will not install on the following Operating Systems:

MS Windows XP; MS Windows 2000 Professional;

MS Windows 9x.

SQL Server can be installed on the following Operating Systems:

MS Windows 2003 Server Standard Edition; MS Windows 2003 Server Enterprise Edition;

MS Windows 2000 Server;

MS Windows 2000 Advanced Server.

document.doc



8/63


2 Installing SQL Server Client Tools

In order to be able to access the SQL server using the Software Manager within Wise we require the SQL Client Tools to be installed locally.

So run the SQL Client Tools executable and follow the procedure outlined below.

1The following screen appears.

Select “SQL Server 2000 Components”.

2 Select “Install Database Server”.

document.doc



9/63


3The following error occurs.

Click on “Ok”.

4 Click on “Next”.


document.doc



10/63



7Fill in for “Name” and “Company” the value “Alliance & Leicester Group”.

Click on “Next”.

document.doc



11/63


8 To accept the Software License Agreement click on “Yes”.

9Select “Client Tools Only”.


document.doc



12/63


10 Leave as “Default” and click on “Next”.


document.doc



13/63


12Click on “Finish”.

document.doc



14/63


3 Installation of Wise Package Studio v5.6 on Packaging Machine

Here the installation of Wise Package Studio is described on your local packaging machine, be sure to use the .MSI based installation of Wise Package Studio and not the .EXE based installation.

3.1 Wise Package Studio v5.6

The .MSI based installation can be found on the S:\Utils Run the Installation .MSI and follow the procedure explained below.

Wise Support Site: http://support.wise.com

1After starting the .MSI based installation, the following screen appears.


document.doc



15/63

http://support.wise.com/


2Fill in “Alliance & Leicester Group” at “Full Name” and “Organization”, and remove the marks in front of “Install Evaluation Version” and “Register on the Internet”.

At this time two serial numbers must be entered, click on “Add”.

3The serial number that has to be filled in is the “Wise Package Studio 5 Bundle” serial number.

Fill in the number and click on “Add”.

document.doc



16/63


4 When all information is entered, click on “Next”.

5 Select “I accept the license agreement” and click on “Next”.

document.doc



17/63


6Select “Complete” and click on “Next”.

This option is selected, because the server part is installed and not the part for the client.

7 Select “Browse” to change the directory of the Share Point Directory.

document.doc



18/63


8Move the directory to a place where there is enough space for the Wise Share Point.

Example:

“D:\Wise Share Point\”.

Click on “OK”.

9 When the correct directory is selected, click on “Next”.

document.doc



19/63


10 Leave the default directory for Wise Package Studio and click on “Next”.

11 Click “Next” to start installing the application.

document.doc



20/63


12 Wise Package Studio is being installed.

13At this point the selection for using a Microsoft Access or Microsoft SQL Server Database must be made.

Select “Microsoft Access”


document.doc



21/63


14Click “Microsoft SQL Server or Microsoft Data Engine (MSDE)”

Server: ‘<Not yet known> eg.DBGTNSVR01’


15Choose “SQL server Authentication”

Logon ID: sa

Click “SQL Server authentication using a logon ID and password supplied by the user ”

Click “Next”

document.doc



22/63


16Add a user name and password and shown.

Click “Next”

15Leave as default “Unchecked”

Click “Next”

document.doc



23/63


16 The configuration of Wise Package Studio is taking place.

17 Click “Finish” to finalize the installation.

document.doc



24/63


3.2 Merge Modules

DB Standards states that merge modules are not to be used for packaging.

document.doc



25/63


4 Wise Package Studio v5.6 Client

Because Wise Package Studio is used in a Client-Server environment a separate installation of the Client must be installed on the test machine. This installation is an option from the .MSI that is used to install Wise Package Studio on the packaging machine.

4.1 Requirements

The test machine must be a clean build, just the basic XP SP2. This will give the best results when carrying out remote setup captures and is less likely of picking up unwanted system components.

As we have wise already installed on SQL server we can map back to the two required shares.

Wise Package Studio \\200.200.200.??\C$\Program Files\Wise Package Studio\

Wise Share Point \\200.200.200.??\D$\Wise Share Point\

Where ?? equals the last to digits of your packaging machine IP address.

4.2 Installing the Client

On the test machine run the wise Installation .MSI and follow the install procedure outlined below.

document.doc



26/63


1After starting the .MSI based installation, the following screen appears.


2Fill in “Alliance & Leicester Group” at “Full Name” and “Organization”, and remove the marks in front of “Install Evaluation Version” and “Register on the Internet”.

At this time two serial numbers must be entered, click on “Add”.

document.doc



27/63


3The serial number that has to be filled in is the “Wise Package Studio 5.6” serial number.

Fill in the number and click on “Add”.

4 When information is entered, click on “Next”.

document.doc



28/63


5 Select “I accept the license agreement” and click on “Next”.

6Select “Complete” and click on “Next”.

document.doc



29/63


7Leave as default:

“Full Client” and click ‘Next’

Note: “Minimal Client” should be used if capturing applications such as Crystal Reports.

8Click ‘Browse’ and enter the unc path back to the packaging machine.

\\200.200.200.??\D$\Wise Share Point\

document.doc



30/63


9 Click “Next”

10Click ‘Browse’ and enter the unc path back to the packaging machine.

\\200.200.200.??\C$\Program Files\Wise Package Studio\

document.doc



31/63


11 Click “Next”

12 Click “Next”

document.doc



32/63


13 Wise Package Studio Client 5.6 is being installed.

14Click “Finish”

Client is now installed on test machine.

document.doc



33/63


5 Configuration Wise Package Studio v5.6

It is also important to configure Wise Package Studio, this configuration must be done from a workstation.

5.1 Initial Workbench Setup

Start Wise Package Studio and go to the “Projects” tab. There are the steps mentioned, that are required, to configure Wise Package Studio.

document.doc



34/63


6.1.2 Define SetupCapture Standards

1At this time the standard for a SetupCapture are defined.

Run the “SetupCapture Configuration” tool.


document.doc



35/63


2At this time the standards for capturing files and registry keys should be changed.

Select the following options:

Allow root to be watched during capture;

Capture non-Microsoft ODBC information;

Generate Both HTML and comma delimited reports.

Note: “Capture changes in hardware registry entries” must be selected for application that require hardware.


document.doc



36/63


3Select as directory to watch “C:\” with all subdirectories.


7It is very helpful to build an exclusion list. Specific files and registry keys are left out of the capture that are definitely not part of the SetupCapture.

Select “Automatically build exclusion list (Recommended)” and click on “Next”.

document.doc



37/63


8 To start the Exclusion Capture click on “Next”.

9 At this time all files and registry keys are scanned and selected witch can be excluded.

document.doc



38/63


10There are also several applications that are used when creating a capture, start those applications, such as:

Notepad; Internet Explorer;

Microsoft Paint;

Wordpad;

A reboot from the PC, for possible hardware changes.

When the PC is restarted this screen appears again, and then click on “Next”.

11 Now a list of files and folders is displayed that are excluded from the SetupCapture. At this time it is also possible to add file and/or folders to the exclusion list.

document.doc



39/63


12 Now a list of registry keys is displayed that are excluded from the SetupCapture. At this time it is also possible to add registry keys to the exclusion list.

13 You can also select .INI files that should be excluded from the Capture.

document.doc



40/63


14At a later time it is recommended to create a Virtual OS file.

With this file you can do a Virtual SetupCapture.

15 Click “Finish” to end the SetupCapture Configuration.

document.doc



41/63


Customize Windows Installer Options

1Open Windows Installer.

On the tool bar go to ‘Tools’ then ‘Options’

This screen should appear.

Click ‘Installation Expert’ option.

document.doc



42/63


2Tick the boxes as shown opposite.

Then click ‘OK’

3Click on the Advertising menu.

Uncheck the “Automatically add Self-registration” tick box.

From the drop down box select

“Scan advertising information into advertising tables”

Then click “Ok”

document.doc



43/63


5.2 Configuration Tools Tab

1In the Tools tab there are several tools that we don’t use and can’t use because there is no IIS server installed.

Those tool should be remove. Go to the edit menu and select the option “Tools”.

2 The configuration screen appears, with on the right the specific settings that can be made for that specific tool.

document.doc



44/63


3 Select the tool “Application GateWay” and set a mark in front of the option “Hide from Tools tab in Workbench.

4Select the tool “Preflight Analysis” and set a mark in front of the option “Hide from Tools tab in Workbench”.

Click on “Close” to finish the Tool setup.

document.doc



45/63


5.3 Preferences

There are also some preferences that should be set, go in the Edit menu to the option “Preferences”.

1The Preferences that should be set on the general tab are:

Active Project Filter; Check for Updates;

Run all tools in Full Screen Mode;

Create backup copy during save.

2 After setting the values it should look like the screen on the right.

document.doc



46/63


3 In the Prompts tab are the prompts displayed that are suppressed. Select all prompts and click on “Activate” to activate all prompts.

4In the Repository tab the Share Point should be set to \\<servername>\Wise Share Point (it is possible that the server name is different on your location).

Click on “OK’ to accept the preferences.

document.doc



47/63


5.4 Process Templates Setup

The Process Template makes sure that everyone works like the same process, go in the Edit menu to the option “Process Templates”.

1Create a new Process according to the specified information.

With right clicking the newly created task it is possible to move to the right (make a submenu item).

2

document.doc



48/63


3

4

document.doc



49/63


5

6 The servername “WSP002” is probably different on your location.

document.doc



50/63


7 The servername “WSP002” is probably different on your location.

8

document.doc



51/63


9

10

document.doc



52/63


11

12

document.doc



53/63


13

14

document.doc



54/63


15

16

document.doc



55/63


17

18

document.doc



56/63


19

20

document.doc



57/63


21

5.5 Project Setup

It is also very good to create a template that can be used for creating projects in Wise, go in the Edit menu to the option “Project”.

1There are two standard projects in the Project Setup. The “Initial Workbench Setup” you can’t and may not delete! The “Sample Project” you may delete.

Create a new Project and call it “_Default Project Template”. The _ makes sure that is stays on top of the list when you want to create a new project.

document.doc



58/63


2 Look at the picture on the right and use that information to create the “_Default Project Template”.

3A completely filled in Project should look like the one of Microsoft Visio 2002.

This configuration makes sure that everything is generated automatically and that the application is imported in the ConflictManager under a normal display structure.

document.doc



59/63


A 1.1 Modifying the System DSN

1Because the type of authentication has changed, the System DSN has to be edited.

Select the Data Source “Workbench Database” and click on “Configure…”.


document.doc



60/63


3Select the options “With SQL Server Authentication using a login ID and password entered by the user” and “Connect to SQL Server to obtain default settings for the additional configuration options”.

As username and password use the one you just created.

Here it is “Wise User”.Click on “Next”.

4Select the option “Change the default database to” and select from the pull down menu the database “Workbench Database”.


document.doc



61/63


5 Leave all settings as default and click on “Finish”.

6 Click on “Test Data Source” to test if the connection functions.

document.doc



62/63


7If the connection is correctly configured the message “Test Completed successfully”.

Click on “OK”.

A 1.2 Registry Setup

A registry has to be entered/modified into the registry to finalize the configuration.

The registry key “HKEY_Current_User\Software\Wise Solutions\Workbench\Recent File List” contains a key with the default value “DSN=Workbench Database”.

Change this value into: “DSN=Workbench Database; UID=Wise User; PWD=

The UID should be “sa”, the default SQL Server user, or any other valid SQL Server user that exists in the Workbench Database.

document.doc



63/63

Documents

DB Installation Manual Wise v5.6 v1.0