Documentos de Académico
Documentos de Profesional
Documentos de Cultura
3M
Installation and Upgrade Guide
Contents
Introduction and setup overview .................................................................................................... 1
About this guide ............................................................................................................................ 1
Chapter 1 Pre-installation checklist............................................................................................ 3
Chapter 2 Server installation requirements ................................................................................ 5
3M Command Center server requirements .................................................................................. 5
Operating system....................................................................................................................... 5
Processor ................................................................................................................................. 5
Memory..................................................................................................................................... 5
Disk space................................................................................................................................. 5
Database server requirements .................................................................................................... 5
Application server prerequisites .................................................................................................. 7
Installation security requirements ................................................................................................ 12
Networking requirements............................................................................................................ 12
Node requirements........................................................................................................................ 13
Node version requirements......................................................................................................... 13
3M SelfCheck System and 3M Intelligent Return and Sorter System Node
Requirements .......................................................................................................................... 14
Chapter 3 Installation Procedure ................................................................................................ 15
Chapter 4 Application quick start guide .................................................................................... 19
Chapter 5 Upgrading your Command Center installation ........................................................... 27
Appendix A Troubleshooting...................................................................................................... 31
Node registration failures ............................................................................................................... 31
Node Disconnected Status ............................................................................................................ 31
Web application is not responding ................................................................................................. 31
SQL server is not responding ......................................................................................................... 32
Statistics are not updating.............................................................................................................. 32
Appendix B Installing SQL server ................................................................................................ 33
Appendix C Backing up your Command Center database ........................................................... 37
3M-CIMS database backup best practices ...................................................................................... 37
Appendix D Command Center migration ..................................................................................... 39
Move Command Center database to a different SQL server ............................................................. 39
Move Command Center to a different server ................................................................................... 39
Appendix E Re-registering, archiving and moving nodes............................................................ 41
Re-Register nodes ........................................................................................................................ 41
Archive and move nodes ............................................................................................................... 42
Appendix F Command Center configuration utility...................................................................... 45
Database ...................................................................................................................................... 45
User accounts ............................................................................................................................... 46
Server .......................................................................................................................................... 47
Update server name/address ...................................................................................................... 48
Warranty ......................................................................................................................................... 51
3M Service ...................................................................................................................................... 53
Contents
ii
Description
Complete
(x)
Important: Establish the name of the server before you register any nodes
(e.g. SelfCheck systems).
The default registration process passes the name of the server to the node.
The node uses this name for all future communications with the server. For
easier installation, ensure that all nodes can ping the name (or IP Address
if you are not using DNS resolution) of the server prior to installation. You
may need to enable ping (ICMP) on your server.
To use a static IP address instead of a resolvable name, refer to Appendix F,
which explains how to make this change after installation of the software,
but prior to registration of any nodes.
Domain
Use of port 9090 is required for nodes to be able to communicate with the
server.
Opening of Http port 80 is required for users to launch the web application.
If you access the application over Https, open port 443.
Ensure that port 8080 (not 9090) is open for communication on the nodes
you intend to register with the Command Center server. Also ensure the
functionality on each node you intend to register with the Command Center
server is enabled.
Example: Enable Command Center on the SelfCheck and restart the
SelfCheck System before you register the node. Please refer to the nodes
user guide for more details.
Processor
A dual core or better processor is required.
Memory
2 GB RAM or better is required.
Disk space
20 GB or more available hard disk space is required.
Note that this amount is used for the application and application logging. It does not include space required for database storage.
Disk size
Disk size varies based on the number and type of nodes connected, how long data is stored, and the interval between database
backups.
If you do not perform backups, transaction logs grow indefinitely on non-Express SQL databases. If you do not backup your
database, you will eventually run out of disk space.
Limitations
While planning for your installation, observe the following limitations.
SQL Express 2005/2008 is limited to 4GB disk usage, 1GB RAM and 1 Physical Processor
RAM and Processor limitations effect performance when compared to non-Express installations
SQL Express 2008R2 is limited to 10GB disk usage, 1GB RAM and 1 Physical Processor
RAM and Processor limitations effect performance when compared to non-Express installations
SQL Express is not recommended for long term (2 years or more) use on sites with 25 or more nodes connected.
Security
Mixed mode authentication (Windows authentication and SQL Server authentication mode) must be available.
If an SQL Server is already installed that utilizes only Windows authentication, follow the instructions provided in the following
link to switch to mixed mode authentication.
http://msdn.microsoft.com/en-us/library/ms188670.aspx
Connectivity
If your SQL Server (2005, 2008 or 2008 R2) resides on a server other than your Command Center application (the recommended
configuration) server, ensure that it is configured to allow incoming TCP/IP (or TCP/IP and named pipes) connections. The
following example illustrates the configuration for SQL Server 2005.
General
These prerequisites apply to all Command Center application server installations. The first two are installed by the installation
wizard and require no user action.
1.
Microsoft .Net 4.0 Framework (installed by the installation wizard if not already present).
2.
Microsoft Report Viewer control 10.0 (installed by the installation wizard if not already present).
3.
Distributed Transaction Coordinator (DTC) service must not be disabled. The service need not be started, but is required to
temporarily start the DTC for IIS Virtual directory creation/rollback. The DTC service can be stopped after installation is
complete, since it is not required by Command Center.
4.
Web Server Role has to be installed (via Server manager, Add Roles) with the following role services (via Server manager,
Web Server, Add Role services)
Web Server
Application Development
.Net Extensibility
ASP.NET
ISAPI Filters
ISAP Extensions
Common HTTP Features
Static Content
Default Document
Health Diagnostics
Http Logging
Security
Windows Authentication
Request Filtering
URL Authorization
Management Tools
ILS Management Compatibility
ILS Metabase Compatibility
2.
The following features must be present (via Server Manager, Add Features).
.NET Framework 3.0 features
WCF Activation
HTTP Activation
Windows 7 prerequisites
IIS must be installed. Also, the following windows features must be enabled/installed (via Control Panel, Programs, Programs
and Features, Turn Windows Features On/Off).
Internet Information Services
.Web Management Tools
IIS 6 Management Compatibility
IIS Metabase and IIS6 Configuration Compatibility
World Wide Web Services
Application Development Features
.Net Extensibility
ASP.NET
ISAPI Filters
ISAP Extensions
Common HTTP Features
Static Content
Default Document
Health Diagnostics
Http Logging
Security
Windows Authentication
Request Filtering
URL Authorization
Microsoft .NET Framework 3.5.1
Windows Communication Foundation HTTP Activation
10
11
Networking requirements
Prior to installing the Command Center software, ensure that each of the following items has been addressed. This should minimize
post installation issues you may encounter while attempting to register nodes or obtain status calls from nodes.
Server network information (e.g. DNS, WINS, static IP) established at each node that will be connected.
Network connectivity at each node has been tested.
Use a ping test to ensure network connectivity at the nodes.
Ping (called ICMP in most firewall applications) must be enabled on the Command Center server. In most cases, testing
a ping from each physical location is adequate to ensure that nodes can be registered with the server. Some examples are
shown below:
Static IP test ping 192.168.1.100
Hostname DNS test ping ServerName
Fully qualified DNS test ping ServerName.yourlibrary.org
12
Note that the installation attempts to open these ports, but opening them prior to installation is required if a firewall other than
the default Windows Firewall is used.
Node requirements
Enabling a node to communicate with the Command Center server varies based on node type. The following is a list of supported
nodes and instructions for establishing communication with the Command Center server.
13
SelfCheck
System and 3M
Intelligent Return and Sorter System
3M
Node Requirements
Refer to the most recent documentation for the node to resolve any discrepancies with information provided in this guide.
1.
2.
Use a web browser to open the administration software application for the node, then access the Network tab.
e.g. 3M SelfCheck System Manager http://<IPaddress or PCName>/SelfCheck
3.
Scroll down to the following setting and check the Enabled box. Save the change by clicking Save Changes.
4.
14
Record the indicated required settings (or keep the display active while you establish the required settings), then click OK to
abort the installation so you can address any prerequisites. For more information on Command Center server prerequisites,
refer to Chapter 2 Server installation requirements in this guide.
15
2.
If all prerequisites have been met, the 3M Command Center InstallShield Wizard Welcome window appears.
Click Next.
3.
You must accept the license agreement to continue. Select the appropriate option, then click Next.
16
4.
Enter your User Name and Company Name, then click Next.
17
5.
This information is used by the installer to create the 3M-CIMS database, and to run SQL scripts. The installer must have the
proper rights (Windows Authentication) on the SQL Server, or should use an SQL server authentication Login ID that has
appropriate rights, to create the database and run the SQL scripts.
Note that even though the image shows Windows authentication as the choice, you can use SQL Server authentication if
you have an SQL Server user id that has administrator rights. If you experience issues with the installation or connection to
the SQL Server, please ensure you have selected the correct database server and have the appropriate permissions entered.
If these are correct and you still have issues, please review the Minimum Database Server Requirements in Chapter 1, or
contact your Database Administrator.
Enter the SQL Server information, then click Next.
6.
18
2.
Once logged in, you will be prompted to change your password. You can type the same password as the new password if
desired.
Default length for passwords is 6 characters, which must include at least one non-alphanumeric character (e.g., ! @ #
$ % ^ & *).
3.
b.
Locate your license file on the installation disk you received from 3M. If you do not have a 3M Command Center
software license, please contact 3M.
19
c.
After the information is successfully saved, the licensed features and nodes appear.
20
4.
Configure the e-mail server. Configuring the e-mail server enables Command Center to send password resets to users.
a.
b.
c.
Under Web UI Settings, if desired, you may upload a new image to create a custom header for each page.
21
5.
6.
22
Configure the e-mail address for the superadmin user. This is the address a password reset will be sent to.
a.
b.
c.
Change the e-mail address to your own e-mail address, then click Save.
b.
Select 3M CIMS Customer, then change the Location Name and Description for the top parent level of your library
system.
c.
Click Save.
d.
e.
Add a location by entering a Parent location, Location Name and an optional Description for each location, then
click Add.
3M 2011. All rights reserved.
f.
7.
Add additional locations to build an appropriate hierarchy for the library network by clicking Click Here after each
location is added.
Register nodes (new devices). Nodes consist of SelfChecks, IRSs, Model 9100 Detection Systems, or a network device.
a.
b.
Enter the Node name, Network address, Location and Node type, then click Register.
Note: After registering a new system node, it may take a few minutes to a few days to copy all the statistics, depending
on the amount of statistical history on your system.
Note: If you prefer not to wait for automated synchronization of a node, synchronize the node manually. Select
Statistics, then Statistics collection status, then Manual statistics sync. The Request Statistics Data
Synchronization window appears.
.
Select a location/node, Node type, and Sync Start Date are required fields. Specify appropriate values for the
synchronization, then click Send Sync Request.
c.
23
8.
9.
a.
b.
Enter a new role under Add a new role, then click Add.
c.
Once a role appears on the role list, click on the role to access a list of features available for the role and to configure
the role.
d.
Add users.
a.
24
b.
10.
Enter the appropriate information for a new user, then click Save.
b.
Enter a Name and Url for the new line, then click Add link.
25
26
WARNING Failure to back up the 3M-CIMS database prior to an upgrade can result in a loss of data if the installation
is unexpectedly disrupted (loss of power, connectivity, OS restart, etc.). It is highly recommended that you first back up your
current 3M-CIMS database prior to proceeding with the installation of the Command Center software.
Complete the following steps to upgrade the 3M Command Center software.
1.
2.
27
If all prerequisites are met, the InstallShield Wizard welcome window appears.
3.
If you have created a backup of your 3M-CIMS SQL Server database, click Yes.
The 3M Command Center InstallShield Wizard Welcome window appears.
4.
Click Next.
The license agreement appears.
28
5.
You must accept the license agreement to continue. Select the appropriate option, then click Next.
The Customer Information window appears.
6.
Enter your User Name and Company Name, then click Next.
The Choose Destination Location window appears.
29
7.
To change the location of the installation, click Change. When you are satisfied with the location for the installation,
click Next.
The Database Server window appears.
This information is used by the installer to run SQL upgrade scripts. The installer must have the proper rights (Windows
Authentication) on the SQL Server, or should use a SQL server authentication Login ID that has appropriate rights to
run the SQL scripts.
Note that even though the image shows Windows authentication as the choice, you can use SQL Server authentication if
you have an SQL Server user id with administrator rights.
WARNING Ensure that you specify the same instance of SQL Server that contains the 3M-CIMS database
you wish to upgrade.
If you experience issues with the installation or connection to the SQL Server, please ensure you have selected the correct
database server and have the appropriate permissions entered. If these are correct and you still have issues, contact your
Database Administrator.
8.
9.
30
Appendix A Troubleshooting
Node registration failures
If you receive an Unable/Failed To Register The Node error while registering a node, complete the following steps.
1.
Review the Networking Requirements in this guide (see Chapter 2 Server installation requirements).
2.
Review the Node Requirements in this guide (see Chapter 2 Server installation requirements).
3.
Ping the server from the node (the server must allow pinging for this test to work).
4.
Restart the nodes application and attempt to register the node again.
Ensure that the node is powered on and the node application (e.g. SelfCheck system) is running.
2.
Ensure that TCP port 9090 is open for network traffic on the 3M Command Center server.
3.
Ping the server from the node (the server must allow pinging for this test to work).
4.
If the node is on a different subnet and not in the same domain as the 3M Command Center server, ensure that the WINS
setting on the node has a WINS server name (this is located in the same directory as your route table). This allows the node to
perform name resolution for the 3M Command Center server using the WINS server.
Note that this is not an issue if all nodes exist on the same domain as the server, or if you are using static IP addresses.
5.
Restart the nodes application (not the PC) to see if this resolves the communication issue.
6.
If the nodes IP address has changed, or the nodes host PC has been replaced, see Appendix E Re-registering, archiving
and moving nodes.
2.
Ensure that TCP Port 80 or 443 (if you are using SSL) is open and not being blocked by a firewall on the Command
Center server.
3.
Review the Application Server Prerequisites in this guide and ensure that each has been met (see Chapter 2 Server
installation requirements.
31
Appendix A Troubleshooting
2.
Review the Minimum Database Server Requirements (see Chapter 2 Server installation requirements) and ensure that
each has been met.
3.
If this is a new SQL Server installation, review the steps for Installing an SQL Server (Appendix B Installing SQL server).
4.
Check the status of the Statistics collection in the Command Center application. If the collection status is green, it may be
behind in statistics collection (usually the case when a new node with a significant amount of historical data is first added).
2.
Check the connectivity between the node and the server. Ping the node from the server (the node must allow ICMP traffic for
this to work).
3.
Ping the server from the node (the server must allow ICMP traffic for this test to work).
32
Run SQL Server Express 2008 R2 .exe from the Command Center installation disk. The name of the .exe file is shown below.
SQLEXPRWT_x86_ENU.exe
If you do not have an installation disk, download the software from the Microsoft website.
2.
33
3.
Enable the features outlined in the example. If you wish to change the installation directory, click ....
4.
34
5.
35
6.
36
37
Useful Links
The following links are provided by Microsoft.
Backing Up and Restoring Databases in SQL Server - http://msdn.microsoft.com/en-us/library/ms187048.aspx.
SQL Server 2008 R2 http://msdn.microsoft.com/en-us/library/ms187048(v=SQL.105).aspx
SQL Server 2008 http://msdn.microsoft.com/en-us/library/ms187048(v=SQL.100).aspx.
SQL Server 2005 http://msdn.microsoft.com/en-us/library/ms187048(v=SQL.90).aspx.
How to back up a database using SQL Server Management Studio - http://msdn.microsoft.com/en-us/library/ms187510.aspx.
SQL Server 2008 R2 http://msdn.microsoft.com/en-us/library/ms187510(v=SQL.105).aspx.
SQL Server 2008 http://msdn.microsoft.com/en-us/library/ms187510(v=SQL.100).aspx.
SQL Server 2005 http://msdn.microsoft.com/en-us/library/ms187510(v=SQL.90).aspx.
How to back up a database using Transact SQL - http://msdn.microsoft.com/en-us/library/ms191304.aspx.
SQL Server 2008 R2 http://msdn.microsoft.com/en-us/library/ms191304(v=SQL.105).aspx.
SQL Server 2008 http://msdn.microsoft.com/en-us/library/ms191304(v=SQL.100).aspx.
SQL Server 2005 http://msdn.microsoft.com/en-us/library/ms191304(v=SQL.90).aspx.
Open SQL Server Management Studio and connect to the SQL Server Express instance.
2.
3.
4.
Click Tasks, then Backup menu option. Record the backup location and file name.
5.
6.
Copy the backup file to a network location, or to a removable media (ex. flash drive).
38
Ensure that mixed mode authentication is enabled on the new SQL server.
2.
Add an SQL Server login with the name 3MCIMSUser and a password of your choice.
3.
4.
Copy the 3M-CIMS.mdf file over to the data folder of the new SQL server.
5.
Attach the 3M-CIMS.mdf file as the 3M-CIMS database on the new SQL server.
6.
Delete the 3MCIMSUser under the 3M-CIMS database users (not the one that you created in Step 2).
7.
Open up the user mapping dialog (right click Properties, then User mapping) for the 3MCIMSUser you created, and map it
to 3M-CIMS database and the 3MCIMSAppRole database role.
8.
Access the Command Center configuration utility (see Appendix F) and change the database connection information (server
and user id/password), then save the changes. Restart the service when you are asked for a confirmation during the save (or
you will have to do it manually).
If needed, record the SQL server instance name using the Command Center configuration utility (see Appendix F).
2.
3.
Install Command Center on the new server. Ensure that you provide the same SQL server instance for the new installation.
4.
Open the Command Center configuration utility and click the Server tab.
Change the Server name to the new server and save the change. This name is used by the nodes (SelfCheck, IRSS, Detection
System, etc.) to connect to the server and send status information.
5.
Restart the service when asked for a confirmation during the save (or you will have to do it manually).
6.
7.
Select the Publish Server address option, then click Publish server address. The system attempts to propagate the
name change to all nodes.
39
40
Log into Command Center with the appropriate mode management access level.
2.
3.
4.
41
Log into Command Center with the appropriate node management access level.
2.
3.
Click Archive.
4.
If you only want to archive the node, stop here. If you want to now move the archived node, complete the following steps.
5.
6.
Click Move.
42
7.
Complete the registration information for the node at its new location, then click Register.
Once a node has been moved, all new statistics collected by the node are associated with the new location.
43
44
Database
The Database tab is intended for the following tasks.
Migrating the Command Center database to another SQL server instance (see Appendix D for more information).
Updating SQL server login information.
Testing the connection to your SQL server database.
45
User accounts
The User Accounts tab is intended for the following tasks.
If you forget your superadmin account password and do not know the email address for it, use the configuration utility to change
the email address and password of the superadmin account.
To adjust the Password Policy for user accounts.
46
Server
The Server tab is intended for the following administrative tasks.
Updating the Command Center server name and address.
To specify a Load Balance configuration. For more details on Load Balancing considerations and support, please contact 3M.
47
Access the Command Center configuration utility, then click the Server tab.
2.
Change the Server name and save the change. The Server name is the name used by the nodes (SelfCheck, IRSS, Detection
System, etc.) to connect to the server and send status information.
3.
Restart the service when asked for a confirmation during the save (otherwise you will have to do it manually).
4.
5.
Select Publish Server address, then select either Single Node or All active registered nodes.
6.
Click Publish server address. This attempts to propagate the name change to all nodes, or to the single node selected in
the Select node list.
The results are displayed in new window.
48
49
50
Warranty
Effective 12-12-05
One Year Library Systems Product Performance Guarantee: Subject to the Limitation of Liability below, 3M guarantees your
satisfaction with the performance of any 3M Library System Product for 12 months from the date of installation provided that a)
you are the original purchaser: b) you have executed a one (1) year 3M Service Agreement for maintenance of the Library System
product; and c) the product has not been subjected to abuse, misuse, accident or neglect. Performance means the product meets 3M
published product specifications. If you are not completely satisfied with the performance of your Library System Product, you
may return the Library System product for a prompt refund. 3M will pay all reasonable de-installation and shipping charges to
return the product to 3M. Note that all claims under this guarantee must be submitted to 3M within 12 months from the date of
installation of the 3M Library Systems Product. Failure to submit a claim within this time frame will invalidate this guarantee.
IMPORTANT: Consumables and non-3M branded products are excluded from this Guarantee.
Warranty and Limited Remedy for Non-Software Library Systems Products Not Covered by Performance Guarantee: Unless
stated otherwise in 3M product literature or packaging, 3M warrants that each 3M Library Systems Product meets the applicable
specifications for a period of ninety (90) days from the date of shipment (or, in the case of hardware installed by 3M, from the
date of installation). Any warranties related to 3M software are contained in separate 3M software licenses. Consumables and
non-3M branded products are excluded from this Warranty and Limited Remedy.
3M MAKES NO OTHER GUARANTEES, WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE OR ANY IMPLIED WARRANTY OR CONDITION ARISING OUT OF A COURSE
OF DEALING, CUSTOM OR USAGE OF TRADE. You are responsible for determining whether the 3M product is fit for a
particular purpose and suitable for your application. If the 3M product is defective within the warranty period and provided that
a) the product has not been subjected to abuse, misuse, accident or neglect and b) you have notified 3M within thirty (30) days
after the defect was discovered, your exclusive remedy and 3Ms and sellers sole obligation will be, at 3Ms option, to replace
or repair the defective 3M product.
Limitation of Liability: EXCEPT WHERE PROHIBITED BY LAW, 3M AND SELLER WILL NOT BE LIABLE FOR
ANY LOSS OR DAMAGE ARISING FROM 3M LIBRARY SYSTEMs, WHETHER DIRECT, INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL, REGARDLESS OF THE LEGAL THEORY ASSERTED, INCLUDING
WARRANTY, CONTRACT, NEGLIGENCE OR STRICT LIABILITY.
Guarantee and Warranty Claims: For guarantee and warranty claims, and for service, contact our service representatives at
1-800-328-0067
3M Library Systems
3M Center Building 225-4N-14
St. Paul, MN 55144-1000
Ver121205
51
Warranty
52
3M Service
Information to gather
Before you call for service, please have following information available:
The name, address, and telephone number of your facility
A description of the problem or the issue you want addressed
The model number and serial number of the equipment (located on the serial label), if the call is in regard to a system problem
Model Number _________________________
Serial Number _________________________
In Canada
In other countries
1-800-328-0067
English 1-800-268-6235
Franais 1-800-567-3193
53
3M Library Systems
3M Center, Building 225-4N-14
St. Paul, MN 55144-1000
www.3M.com/library