Steps to configure the CA Asset Portfolio Management 12.9 or 14.1 application to connect to a new database

Products

CA IT Asset Manager ASSET PORTFOLIO MGMT- SERVER CA Service Management - Asset Portfolio Management

Issue/Introduction

This document details the configuration steps necessary to re-configure a CA Asset Portfolio Management 12.9 or 14.1 (APM) application to use a new SQL Server database.

If APM is also integrated with CA Software Asset Management, and you wish to demote both environments to another environment, then please contact support for assistance.

Environment

Release: 12.9 and higher

Component: CA IT Asset Manager

Resolution

1. Backup and restore the database from the original SQL Server to a new SQL Server machine.

2. On the APM application server, stop the CA Asset Portfolio Manager services

3. On the APM application server, edit the \Program Files (x86)\CA\ITAM\Application Server\bin\ CA.Common.LoadConfigurationAttributes.dll.config file and update the following entries to match your new SQL Server installation:

<add key="SqlServerVersion" value="MS SQL Server 2012"/> (or "MS SQL Server 2008")

<add key="HostName" value="tcp:[EXAMPLE SQL SERVER],1433"/> (or tcp:[EXAMPLE SQL SERVER]\[EXAMPLE SQL SERVER INSTANCE],[EXAMPLE PORT NUMBER])

Note:

a. the UserID should exist in the new SQL Server installation, with dbowner rights to the mdb database. If it does not, create this user with the proper rights.

b. the password is encrypted. To encrypt passwords, review KB Article 139049

4. Close and save the CA.Common.LoadConfigurationAttributes.dll.config file.

5. Copy the CA.Common.LoadConfigurationAttributes.dll.config file and replace it in the following directories:

\Program Files (x86)\CA\ITAM\Data Importer

\Program Files (x86)\CA\ITAM\Data Importer Engine

\Program Files (x86)\CA\ITAM\Export Service

\Program Files (x86)\CA\ITAM\Event Service

\Program Files (x86)\CA\ITAM\Hardware Engine

\Program Files (x86)\CA\ITAM\Import Driver

\Program Files (x86)\CA\ITAM\Import Processor

\Program Files (x86)\CA\ITAM\Import Service\bin

\Program Files (x86)\CA\ITAM\LDAP Import Sync Service

\Program Files (x86)\CA\ITAM\Registration Service

\Program Files (x86)\CA\ITAM\Storage Manager Service\bin

\Program Files (x86)\CA\ITAM\WCF Service\bin

6. Log onto the APM web server, and also replace the CA.Common.LoadConfigurationAttributes.dll.config file in this directory: \Program Files (x86)\CA\ITAM\Web Server\bin

7. Launch SQL Server Management studio, and run this query against the new mdb:

select * from al_cdb_configurationparameters where componentkey = 'Database'

Review the data in the configvalue column, where configkey = DatabaseOwner, DbInstance, DbLogin, DbNameTxt, DbPassword, DbTcpIpPort, HostName and SqlServerVersionddl. (DbInstance is blank if you are using the default instance).

Here is an example query to update the HostName row:

update al_cdb_configurationparameters set configvalue = '[EXAMPLE NEW SQL SERVER]' where configvalue = '[EXAMPLE OLD SQL SERVER]'

Run sql updates to update the configvalues, as appropriate for your installation.

8. Optional: The machineName column in the al_cdb_configurationparameters table will still reference the machine name that originated the install. These entries will not effect the APM operation in the new environment; however, the Administration -> system configuration -> Application server, and Web server entries will display the, now incorrect, machine names. You may update the machineName column for the specific component key, like Application_Server and Web_Server, to their new values.

9. From a command prompt, perform an IISRESET on BOTH the APM web and APM application servers

10. Login to the APM application, navigate to Administration -> System Configuration -> Database, and verify the entries.

11. Start the CA Asset Portfolio Management services.