Install CA IT Asset Manager 14.1.01
Complete the following steps to apply the cumulative patch to CA IT Asset Manager 14.1:
casm1401
Complete the following steps to apply the cumulative patch to CA IT Asset Manager 14.1:
3
Verify the Prerequisites
- To apply cumulative patch 14.1.01, you must have already installed CA APM 14.1 GA.
- If you have installed CA APM 12.9, you must first upgrade to CA APM 14.1 and then apply the cumulative patch.
Install the Patch
Follow these steps:
- Download the CA APM 14.1.01 cumulative patch from CA Support Online to the CA APM application server in the APM_14_1_01 folder.
- Run the cazipxp.exe –u RO80262.caz command to unzip the CA APM 14.1.01 cumulative patch (caz file) in the same folder:
- Verify that the following files are available:
- MDB.exe
- Setup.bat
- Patch.msp
- Double click and extract ‘MDB.exe’ to get MDB folder.
- Complete the following steps to update the web server, application server components and database.Please apply the Database patch first and then apply the patch in the application and webserver components.
- Log in to the application server where you downloaded and extracted the patch. From the command prompt, go to the APM_14_1_01 folder. To apply the database patch, use the following command.We recommend that you back up your MDB database before you perform the MDB update. If your MDB update fails, restore the backup and start the installation again. We do not recommend that you reinstall the MDB update in the same environment where the MDB update failed.ForSQL Server, execute the following command:setup.bat -SERVERTYPE=DB -DBVENDOR=mssql -DBNAME=<mdb_name> -DBHOST=<database_hostname> -DBUSER=<database_username> -DBPASSWORD=<database_password> -MANIFEST=Unicenter_Asset_Portfolio_Management -WORKSPACE=UAPMSERVERTYPESERVERTYPE is DB, for database patch application.DBVENDORSpecifies the database vendor name. Enter mssql for SQL Server.DBNAMESpecifies the existing CA APM Release 14.1 MDB database name.DBHOSTSpecifies the database server system host name.DBUSERSpecifies the existing CA APM Release 14.1 MDB database user name.DBPASSWORDSpecifies the existing CA APM Release 14.1 MDB database password.The -DBUSER and -DBPASSWORD parameter values must match your existing CA APM Release 14.1 database user name and password.MANIFESTSpecifies the name of the manifest file. Do not change the default value for this parameter.WORKSPACESpecifies the name of the workspace. Do not change the default value for this parameter.ForOracle Server, execute the following command:setup.bat -SERVERTYPE=DB -DBVENDOR=oracle -DBNAME=<oracle_service_name> -DBHOST=<database_hostname> -DBUSER=<database_username> -ORA_TBLSPACE_PATH=<tablespace_path> -DBPASSWORD=<database_password> -MDB_ADMIN_PSWD=<mdb_administrator_password> -MANIFEST=Unicenter_Asset_Portfolio_Management -WORKSPACE=UAPMSERVERTYPESERVERTYPE is DB, for database patch application.DBVENDORSpecifies the database vendor name. Enter oracle for Oracle.DBNAMESpecifies the existing Oracle Service name.DBHOSTSpecifies the database server system host name.DBUSERSpecifies the existing Oracle database user name.ORA_TBLSPACE_PATHSpecifies the path to the Oracle tablespace.DBPASSWORDSpecifies the existing Oracle database passwordThe -DBUSER and -DBPASSWORD parameter values must match your existing CA APM Release 14.1 database user name and password.MDB_ADMIN_PSWDSpecifies the existing MDB administrator password.MANIFESTSpecifies the name of the manifest file. Do not change the default value for this parameter.WORKSPACESpecifies the name of the workspace. Do not change the default value for this parameter.
- To update the application server, copy the folder APM_14_1_01 to the Application server. In the command prompt, go to the APM_14_1_01 folder and run the following command.Setup.bat -SERVERTYPE=APPIf the Application server and the Web server components reside on the same Machine, you can ignore step 7.
- To update the web server, copy the folder APM_14_1_01 to the Web server. In the command prompt, go to the APM_14_1_01 folder and run the following command.Setup.bat -SERVERTYPE=WEB
Verify the Cumulative Patch Installation
After you have completed all installation procedures, you can verify that CA APM 14.1.01 and the database upgrade were performed successfully.
Database upgrade verification
- Login to the server where you downloaded and extracted the CA APM 14.1.01 cumulative patch.
- Navigate to the folder where you downloaded and extracted the CA APM 14.1.01 cumulative patch (APM_14_1_01).
- Navigate to the MDB\mdb1.5 folder.
- Open the install_<databasename>.log file with a text editor.In the log file name, database name is replaced with the name of the database. For example, if the database name is test, the log file name is install_test.log.
- Verify that a message similar to the following message appears at the end of the log file:'MDB setup completed successfully'.
Cumulative Patch verification
- Login to APM application.
- After a successful login click on ‘About’ link (top-right).The display should be:Release:14.1.1.28
- Verify the ITAMMSP.log file in the system drive.
- In the Add/Remove Programs, click View Installed Updates and verify the entryCA ITAM 14.1.01.
Install Localization Update on the Cumulative Patch
After you verify the cumulative patch installation, you must install the localization update for languages other than English.
Follow these steps:
- Log in to the Application Server.
- In the Windows command prompt, navigate to <ITAM installation folder>\L10N\language_pack.
- Run the following command:SetSeeddata.exe <language code-country code>For example, SetSeeddata.exe de_DE. The language codes are same as the folder names present at this location.
- Verify the LOGSetSeeddata.log file.
Uninstall CA APM 14.1.01
You can decide to uninstall CA APM from a computer for various reasons. For example, you can uninstall CA APM because you decided to use the computer for a different purpose or to move the components to another computer.
The MDB upgrade cannot be reverted. To revert the MDB changes, restore the previous database backup.
Follow these steps:
- Login to the servers (Application & Web) where you installed CA APM 14.1.01.
- Go to Control Panel > Programs and Features and click View installed updates.
- Right-click on CA ITAM 14.1.01 and select Uninstall to uninstall this cumulative patch.
Enhancements
Ensure that you read the enhancements and new features available for CA APM, after applying this patch.
Maintenances
Cumulative# | Testfix# | Title | Description |
APM 14.1.01 | T5E2402 | NON ADMIN USERS FAILS TO LOG IN | Issue with non admin users logging into APM. |
T5M7130 | CAN'T UPDATE COST RECORD | Unable to update cost record extensions. | |
T5E2402 | METADATA DOESN'T FRESH ON ALL SERVERS IN LOAD BALANCING ENVIRONMENT. | In NLB environment, extensions created from one server are not available from other server without resetting IIS. | |
NA | INTERNET EXPLORER RENDERING. | Internet explorer rendering issues. | |
NA | PATCH OVERRIDING IIS SETTINGS AND ENABLING WINDOWS AUTHENTICATION. | Patch overriding IIS settings and enabling windows authentication. | |
NA | IP ADDRESSES NOT SHARED | IP no synced with SAM and APM. | |
T5E2404 | UNABLE TO UPDATE ASSET SECONDARY LOOKUP | Unable to update Location and Contact as secondary lookup of an asset. | |
NA | MAC ADDRESS FIELD SMALL | MAC address coming from SAM update. | |
T5E2402 | INACTIVATE ROLE | Unable to save set role to inactive. | |
T5GJ134 | CLEAR EXCEPTION MESSAGE NOT DISPLAYED | Import job errors out with inappropriate Exception message. | |
T5E2408 | ITAM-12.9-INVALID CA_ASSET ROWS | Data importer job fails to create an asset. | |
T5XU059 | DATA IMPORT LOG FILES LINE NUMBER ISSUE | Issue with data importer log files. | |
T5E2404 | UNABLE TO UPDATE ASSET SECONDARY LOOKUP | Unable to update Location and Contact as secondary lookup of an asset. | |
T5GJ138 | [CONFIGURATION] CANNOT REMOVE FOREIGNGROUP LEVEL 2 OR MORE REQUIRED FIELDS. | Unable to remove from the configuration the additional fields associated to related objects. | |
T5E2402 | ITAM - 12.9 - ERROR WHEN CREATING FILTER | Date filter saving issues. | |
T5GJ133 | DATA IMPORTER - IMPROPER LOG RESULTS | Data importer doesn't show log results correctly as processed. | |
T5M7120 | UNABLE TO CLEAR DATE FIELD | Try to import by giving null values for any date field. Get the exception in the log. | |
T5M7120 | ERROR CREATING SEARCHES | The search does not give the Save successful message and also throws an exception when the search is brought up. | |
T5UM103 | LIFECYCLE STATUS DATE CHANGE | The life cycle status date is not changing when the life cycle status is updated. | |
T5UM103 | UNHANDLE SQL EXCEPTION | Infrequent error when using APM. | |
T5GJ140 | UNABLE TO SAVE ANY EXISTING CONTACT RECORDS | The application encountered an error while saving an object that references other objects. Contact ID contains invalid reference key. | |
T5M712 | EXTENDED FIELD NOT SHAREABLE | The extended field should be available for selection. | |
T5GJ137 | HARDWARE RECONCILIATION THROWING ERROR LAST_UPDATE_DATE=NULL | A reconciled computer deleted from ITCM interface and the ITAM Hardware Engine is executed last_update_date to NULL. | |
T5EM232 | CANNOT DELETE FIELD ON ASSET | Can not delete field from GUI. | |
T5E2406 | ITAM - 12.9 -EVENT SERVICE LIFECYCLE STATUS | NA | |
NA | [WCF] USER SHOULD BE ABLE TO UPDATE LAST UPDATE OR CREATION DATES AS NEEDED. | Last update user set up. | |
T5M7125 | UNABLE TO ADD FIELD IN CONF | In Asset Configuration ON mode, we are unable to add Legal Status History Fields to Legal Documents for Assets. | |
T5GJ135 | HIDE INTERNAL ATTRIBUTES FROM 'ADD EXISTING FIELDS' POPUP - CONFIGURATION | ITAMService.log shows that the code is attempting to add data into the arg_allocation_summary_view table, even though these fields are hidden on the configuration. | |
NA | IMPORT JOB ERROR | Import job errors out with inappropriate Exception message. | |
T5XU050 | READ-ONLY PERMISSIONS ISSUE FOR NON-ADMIN USERS | Read-Only permissions issue for Non-Admin users. | |
T5GJ134 | NULL EXCEPTION MESSAGE IN WEB SERVICE | Exception Message: Web Service threw exception in data importer. | |
T5M7120 | UNABLE TO CLEAR DATE FIELD | When importing by giving null values for any date field. Get the exception in the log. | |
T5JH194 | SORTING IMPORTER JOBS ON JOB ID IN ASCENDING ORDER | Unable to sort Import Jobs on Job Id in Ascending direction. | |
T5EM232 | ERROR ON DEAUTHORIZE | Unable to de authorise user from user management. | |
T5EM232 | AUTHORIZE USERS SEARCH | When searching for authorise users are performing an Or as opposed to an And. | |
T5EM232 | ERROR ON CHANGE MODEL WIZARD | APM fails to run change model wizard, tried to execute a model change from/to the same asset family. | |
T5GJ138 | CANNOT FIND CONTACT/ROLE | Unable to search for the user already existing. | |
NA | HW RECON-LIFECYCLE STATUS ERR | updates are failing and ITAMHWEngine.log is throwing numerous errors. | |
T5UM105 | ISSUE WITH ASSET AUDITS | NA | |
T5UM104 | ISSUE WITH CONFIGURATION: ASSET ENTITLEMENTS | All links in Asset Entitlements do not show in configuration ON mode in software asset. | |
T5UM092 | FILTER VALUES CASE SENSITIVE | Organisation save throws error"The User is not authorized to modify the asset due to the filter". | |
T5EM227 | IMPORT JOB ERROR | Data Importer fails to import assets when main destination object is set to 'Asset (All Families)' | |
T5EM226 | AUTOCOMPLETE NOT WORKING | The autocomplete function is not working on lookup fields in the 'additional information' section of the asset details page. |