CIM Server Installation Manual - COINS Global · COINS Installation Manager (CIM) System CIM Server Installation Manual COINS Construction Industry Solutions (Shaker) Corporation

COINS Installation Manager (CIM) System

CIM Server Installation Manual

COINS

Construction Industry Solutions (Shaker) Corporation

6 Airport Park Blvd., Latham, NY 12110 USA

Phone: 518-242-7200 Fax: 518-242-7298

Email: [email protected]

COINS Information Manager (CIM) System

CIM Server Installation Manual

COPYRIGHT NOTICE: Copyright 2008 Construction Industry Solutions Limited. The contents of this documentation and all other documentation provided is the property of Construction Industry Solutions Limited and is strictly confidential. All rights reserved; no part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the Construction Industry Solutions Limited. Much care has been taken in the preparation of the documentation and Construction Industry Solutions Limited believe that the information given is accurate and reliable. However, no responsibility, financial or otherwise, can be assumed for any errors or consequences arising from the use of the material. Companies, names and data used in examples are fictitious unless otherwise noted. The information contained in this document is subject to change.

Table of Contents Overview ....................................................................................................................................... 5 Create Databases........................................................................................................................... 7 Create Database File Maintenance Entries for Databases....................................................... 9 Set Up on Windows Server ....................................................................................................... 11 Appendix A................................................................................................................................. 13 1. Assign User Rights ............................................................................................................. 13 2. Configure the Progress AppServer Broker for CIM ...................................................... 15 3. Configure the WebSpeed Broker for CIM....................................................................... 22 4. Set Up an InstallShield for CIM........................................................................................ 28

COINS Information Manager (CIM) Overview

6/16/2008 CIM Server Installation 5

Overview Installation of the COINS Information Manager (CIM) server is comprised of three main parts that allow you to:

• Create databases • Create Database File Maintenance entries for databases • Set up on Windows Server

The steps for each of these parts are outlined in this document.

COINS Information Manager (CIM) Overview


COINS Information Manager (CIM) Create Databases


Create Databases

1. Create customni and customwi databases by using customni.st and customwi.st files.

2. Load the customni and customwi files, respectively.

3. Load .d files into customni only (there are no data for wimacs).

4. Load the Sequence file into customni only.

5. In the Services file, create entries for customni and customwi.

COINS Information Manager (CIM) Create Databases


COINS Information Manager (CIM) Create Database F/M Entries for Databases


Create Database File Maintenance Entries for Databases

1. Add databases to Custom.

2. Set to autostart / multi volume.

3. Reference –H/‐S/‐N.

4. If necessary, update –h to allow for more databases.

5. Create connections for all of the appropriate accounting databases to ensure that

the servers come up.

COINS Information Manager (CIM) Create Database F/M Entries for Databases


COINS Information Manager (CIM) Set Up on Windows Server


Set Up on Windows Server

1. Create Network Share for CIM.

2. Determine the user to be used for startup services.

3. Update local security policies to use credentials for the following:

• Log on as a service • Log on as a batch job • Act as part of the operating system • Increase quotas • Create a token object • Replace a process level token

4. Ensure that IIS is configured and running.

5. Create a Scripts virtual directory under inetpub.

• Set permissions for read, run scripts, and execute.

6. Install the application server and WebSpeed.

7. Install the Progress Web Client.

8. Set IIS to use WebSpeed extensions, i.e., Extension name = Webspeed CGI.

• Add required file intetput\scripts\cgiip.exe.

9. Create appserver and wimacs directories under Share.

10. Create pools and data under Share.

11. Copy the compiled code from the latest patch zip to the appserver and wimacs paths.

12. Place installshield and options.ini in the installshield directory under Share.

13. Copy the License file to the appserver directory under Share.

14. Configure the AppServer and WebSpeed brokers, as outlined in Appendix A.

COINS Information Manager (CIM) Set Up on Windows Server


15. Go to the Progress ADM service under Services. Verify the user to be used for startup.

16. Modify the options.ini file.

17. Run InstallShield.

18. Ensure that the brokers are up.

19. Start CIM.

20. Create a Data Path.

21. Create a Pools Path.

22. Go to Workstation Setup. Update the parameters to point to the correct server.

23. Add the AutoSet‐kwords parameter.

24. Under intepub\wwwroot, create a webcim folder.

25. Copy files into the webcim folder.

26. Test the web client.

27. Define the tree, users, doc types, and keywords.

COINS Information Manager (CIM) Appendix A


Appendix A

Configuration of Progress AppServer and WebSpeed Brokers

The process for configuring the Progress AppServer and WebSpeed brokers for CIM has been divided into the following four sections:

1. Assign User Rights 2. Configure the Progress AppServer Broker for CIM 3. Configure the WebSpeed Broker for CIM 4. Set Up an InstallShield for CIM

1. Assign User Rights You must ensure that the Progress service is running under a specific username. This specific user must be assigned certain rights to be able to access network resources or the Progress service. These rights differ slightly depending upon the version of Windows you are using. Below are the steps that must be performed in order to assign these rights in the appropriate version of Windows, i.e., Windows NT or Windows 2000. For Windows NT

1. From Start > Administration > User Manager, select Policies, then select User Rights menu.

2. Check the option Show Advanced User Rights.

3. From the Right option, select the option Log on as a batch job.

4. Click the Add button.

5. Select your NT DOMAIN from List Names From.

6. Click on Show Users.

7. Select the appropriate USER, then click the Add button.

8. From the Right option, select Log on as a service.

9. Repeat Steps 4 through 7 to add other applicable rights.



For Windows 2000

1. Go to Control Panel > Administrative Tools > Local Security Policy.

2. From the left pane, select Local Policy > User Rights Assignment. In the right panel, you must find the following policies: • Log on as a service • Log on as a batch job • Act as part of the operating system • Increase quotas • Create a token object • Replace a process level token

3. Double‐click on each one of the policies listed in the previous step. Add the user

account to which you wish to be able to connect via Progress Explorer to the AdminServer.

Note: These changes require a logout before they can take effect.

4. Continue to the next steps outlined in 2. Configure the Progress AppServer Broker for CIM.



2. Configure the Progress AppServer Broker for CIM

1. Go to Control Panel > Services. Select AdminService for PROGRESS 9.1D (see Figure 1. Services screen).

Figure 1. Services screen

2. Select the Startup button to go to the Startup screen (see Figure 2. Startup screen).

a. Make sure the service is set to start with the user you just created.

b. Ensure that the Password is correct for this user.

c. Click OK.

Figure 2. Startup screen



3. From the Start menu, go to Programs > PROGRESS > Progress Explorer Tool to start the Progress Explorer (see Figure 3. Start Progress Explorer).

Figure 3. Start Progress Explorer

4. After Progress Explorer is open, right click on it and select Add Progress Server to add a Progress server (see Figure 4. Add Progress Server).

Figure 4. Add Progress Server

5. Add localhost as the Progress Server.



6. From the tree menu, right click on localhost, then click Connect to connect to the server (see Figure 5. Connect to Server). You should be prompted to log in to the server and use the username and password under which the service is set to run.

Figure 5. Connect to Server

7. Expand localhost and AppServer on the tree menu. Right click on AppServer, then click New to add a CIM AppServer (see Figure 6. Add an AppServer).

Figure 6. Add an AppServer



8. Enter a Name for the AppServer broker (e.g., ascim) in the popup window (see Figure 7).

Figure 7. New AppServer Popup Window

9. From the tree menu under AppServer, right click on the broker you just created (e.g., ascim), then click Properties (see Figure 8).

Figure 8. Properties path

10. On the Properties screen (see Figure 8), do the following: a. Set the Operating mode to Stateless. b. Enter a Working Directory. – This is usually set to be the same as the

temporary directory. It should be a folder used only by this broker. c. Enter a Port number – This can be any free port. d. Select Auto start – This ensures that the AppServer broker starts with the

Progress service.



Figure 9. Broker Properties screen

11. From the tree menu, expand Broker and select Logging Setting (see Figure 10. Broker Logging Setting screen).

Figure 10. Broker Logging Setting screen

12. On the Logging Setting screen, deselect Append to broker log file. By doing this, the log is prevented from growing too large.



13. From the tree menu, expand Server and select Pool Range (see Figure 11. Server Pool Range screen). • Typically, this is set as shown below in Figure 11. However, the number in

the Maximum servers field should equal what was purchased for the customer.

Figure 11. Server Pool Range screen

14. From the tree menu, select Server, then select Logging Setting (see Figure 12. Server Logging Setting screen). a. Deselect Append to server log file.

Figure 12. Server Logging Setting screen



15. From the tree menu, select Server, then select General (see Figure 13. Server General screen). This is where the main configuration is set.

a. Set the Server startup parameters to connect to the nimacs database only,

using a temporary directory for the working directory.

b. For the PROPATH field, you need to add the appserver, appserver\common, and appserver\db‐trig folders from their saved locations on the server.

Figure 13. Server General screen

16. You should now be able to right click and start the Broker (e.g., ascim) from the tree menu. a. If the Broker does not start, look in the ascim.broker.log and ascim.server.log

in the Progress working directory to investigate and correct any problem, if necessary.

17. Continue to the next steps outlined in 3. Configure the WebSpeed Broker for CIM.



3. Configure the WebSpeed Broker for CIM A number of the steps in this section are the same as those used to configure the AppServer broker.

1. Right click WebSpeed from the left tree menu, then select New (see Figure 14. Add WebSpeed).

Figure 14. Add WebSpeed



2. Enter a Name for the WebSpeed broker (e.g., wscim) in the popup window (Figure 15. New WebSpeed Popup Window).

Figure 15. New WebSpeed Popup Window

3. From the tree menu under WebSpeed, right click on the broker you just created (e.g., ascim), then click Properties (see Figure 16. Broker Properties path).

Figure 16. Broker Properties path

4. On the Properties screen (see Figure 17. Broker Properties screen), do the following:



a. Set the Operating mode to Stateless.

b. Enter a Working Directory. – This is usually set to be the same as the temporary directory. It should be a folder used only by this broker.

c. Select Auto start – This ensures that the WebSpeed broker starts with the

Progress service.

Figure 17. Broker Properties screen

5. From the tree menu, expand Broker and select Logging Setting (see Figure 18. Broker Logging Setting screen).

Figure 18. Broker Logging Setting screen



6. On the Logging Setting screen, deselect Append to broker log file. By doing this,

the log is prevented from growing too large.

7. From the tree menu, expand Agent and select Pool Range (see Figure 19. Agent Pool Range screen).

a. Set the Minimum agents number to start as 1.

b. Set the Maximum agents number to equal what was purchased for the

customer.

Figure 19. Agent Pool Range screen

8. From the tree menu, select Agent, then select Logging Setting (Figure 20. Agent Logging Setting screen).

a. Deselect Append to agent log file.



Figure 20. Agent Logging Setting screen

9. From the tree menu, select Agent, then select General (see Figure 21. Agent General screen). As with the AppServer broker, this is where the main configuration is set.

a. Set the Agent startup parameters to connect to the nimacs and wimacs

databases, using a temporary folder for the working folder.

b. Set a start procedure to imacs‐disp‐91d.p (‐p imacs‐disp‐91d.p).

c. All the folders that need to be added are not fully shown in the PROPATH. You must add the following (in this order): wimacs folder, appserver, appserver\common, and appserver\db‐trig.



Figure 21. Agent General screen

10. The server should now be able to start.

a. If the server does not start, look in the wscim.broker.log and wscim.server.log to investigate and correct any errors, if necessary.

11. Continue to the next steps outlined in Error! Reference source not found..

Note: If you prefer, you may do this configuration by editing the ubroker.properties. The URL to connect to the webservice is: http://<server name>/scripts/cgiip.exe/WService=<broker name>/main.w For example, one setup for development is:



4. Set Up an InstallShield for CIM To set up a CIM InstallShield, you need to configure the options.ini file in the installshield folder. Below is an example of the contents used to configure the development system. [GENERAL] -OPT=APPSERVER -HN=saleslogix -HIP=99.7.5.120 -LOCAL=ON -NT=tcp -SILENT=ON -PV=9.1D -WAN=ON LOAD1=Live [Live] -DESC="COINS TI Image Viewer" -PATH=C:\Program Files\CIM -SPath=\\saleslogix\cim$ -app=ascim -Dpath=\\saleslogix\cim$ -shortcut=CTRL + ALT + L -icon=imacs.ico -FOLDER=COINS TI Image Viewer -ARG=-d mdy In the General section, you must always only edit the servername (‐HN) and server IP (‐HIP) for each customer, and perhaps the Progress version (‐PV), which should be for Progress Webclient 9.1x. If the customer is running more than one environment for CIM, you can add as many sections as you wish (LOAD1, LOAD2, LOAD3, etc.). For each section you add, a subsection must be configured (e.g., Live in this example).

• DESC – The description of the icon used on the desktop. • PATH – Where the local code should be stored. • SPath – The share name of a path where CIM is installed on the server. • DPath – Usually the same as –Spath, but you may store your data in another

Share if you wish to use this parameter. • app – The AppServer brokername configured above. • shortcut – The keyboard shortcut to start CIM. It is not required. • icon – The icon used in the desktop shortcut, usually imacs.ico, but you can

use your own. It must be in the PATH\appserver\clientgui\icons folder. • FOLDER – The program group name added to the Start menu.



• ARG – Allows you to add any custom arguments to the Progress startup command. Typically, this is –d mdy in countries where the date is formatted month/day/year.

It is recommended that you add a fat client on the server to make support easier. Normally, we allow a free license in CIM to account for this.

Documents

CIM Server Installation Manual - COINS Global · COINS Installation Manager (CIM) System CIM Server Installation Manual COINS Construction Industry Solutions (Shaker) Corporation