Upgrading
Smart IT installer supports direct upgrade to Smart IT 20.02 from Smart IT version 1.5.01 and later. Remedy IT Service Management (ITSM) 18.05 with the deployment patch of 20.02 is the minimum supported version for Smart IT 20.02.
Before you begin
The following table provides information about specific scenarios that you should consider prior to upgrading to Smart IT 20.02:
| Scenario | Consideration or action required |
|---|---|
| You are using Remedy with Smart IT 18.05 with latest patch and you have ITSM 18.05 with the deployment patch of 20.02. Now, you plan to upgrade Smart IT 20.02 version. | Perform the following steps: Upgrade to Smart IT 20.02:
|
You are using Remedy with Smart IT 2.0 and BMC Digital Workplace 3.5 with AR ITSM 9.1.x and you plan to upgrade both Smart IT and Digital Workplace to 20.02 version. If you use Smart IT and BMC Digital Workplace both, always upgrade BMC Digital Workplace first. | The Smart IT 20.02 installer provides you the option to upgrade only Smart IT. The Smart IT 20.02 installer does not have an option to upgrade BMC Digital Workplace. Perform the following steps:
Important In case you need to change the AR Server references, make the changes in the SMT:Administration Console form. |
You are using Remedy with Smart IT 2.0 and BMC Digital Workplace 3.5 and you plan to upgrade only Smart IT because you do not use BMC Digital Workplace. | BMC Digital Workplace will no longer be available for use.
Important In case you need to change the AR Server references, make the changes in the SMT:Administration Console form. |
Refer to the following image to know the components that require the deployment package:
Upgrade sequence
Use the following graphic to make decisions about the upgrade and to understand the upgrade sequence:
Note
If you are upgrading from Smart IT 18.05 to Smart IT 20.02, you don't need to run the Social data migration utility while upgrading.
Best practice
- We recommend to upgrade to the latest patch of Smart IT to get the best performance.
- Use a separate database schema for Smart IT and BMC Digital Workplace.
- Install Smart IT and Digital Workplace on separate Apache Tomcat servers.
- Run all the upgrade utilities during the production cut-over activity.
Upgrade process
Smart IT upgrade comprises the following stages:
Before you begin
| Task | Action | Additional information |
|---|---|---|
| 1 | Upgrade BMC Digital Workplace to version 20.02. | If you are using both Remedy with Smart IT and BMC Digital Workplace, you must upgrade BMC Digital Workplace to version 20.02. For instructions, see
Upgrading BMC Digital Workplace
|
| 2 | Install BMC Remedy ITSM version 18.05 and apply the latest deployment package of 20.02. | Before you upgrade Smart IT, you must install BMC Remedy IT Service Management (ITSM) version 18.05 and apply the latest deployment package of 20.02. For instructions, see
Installing BMC Remedy ITSM
|
Stage 1: Prepare to upgrade Smart IT
| Task | Action | Additional information |
|---|---|---|
| 1 | Review the system requirements:
| Make sure that you meet the system requirements for this release. For more information, see System requirements for Smart IT. |
| 2 | Review the known and corrected issues. | See the release notes and notices. |
| 3 | Download the Smart IT installation files. | Find how to obtain the files that you need for installation from the BMC Electronic Product Distribution (EPD) site. |
| 4 | Review the Smart IT performance. | BMC has conducted an analysis of various performance test results and provided performance benchmarking methodology and environment. Recommendations based on the test results. |
| 5 | Complete the upgrade worksheets. | Before installing the products, gather information about the parameters that the installer requires for each product. The planning spreadsheet provided in this section helps you gather these parameter values. This information helps you avoid installation errors, when you run the installation. |
| 6 | Take a backup of Remedy AR server database and Smart IT database. | As a precaution in the event of an upgrade failure, back up both the BMC Remedy with Smart IT database and the BMC Remedy AR Server database. |
| 7 | Upgrade database | Optionally, due to the separation of BMC Digital Workplace and Smart IT products, during the Smart IT upgrade, you need to create new DB schemas/users. The new DB schemas/users will contain only Smart IT data. For more information, see Create databases. The Smart IT installer will create the new DB schemas/users automatically. However, if you have database access restrictions and cannot allow the Smart IT installer to create schemas/users, you can create pre-existing schemas/users. |
| 8 | Migrate your social data. | If you are upgrading from any version earlier than 18.05, you need to migrate your social data as starting from 18.05, MongoDB is no longer used as the database to store your social data. If you need to retain the old social timeline data, migrate your social data from MongoDB to the AR System. This migration ensures that the data is displayed seamlessly on the Smart IT dashboard after the upgrade. |
| 9 | Upgrade to 64-bit Java Runtime Environment (JRE) 8 or above version. | Upgrade to JRE 8 or above version on all the servers where Smart IT is installed. For information about downloading JRE 8, see http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html in the Oracle documentation. Note: If users want to change Java to Open JDK 11 or 12 for Smart IT, then they need to manually remove remove "-XX:+UseParNewGC" parameter from the Java options. |
| 10 | Upgrade to Remedy Single Sign-On. | Smart IT does not support Atrium Single Sign-On (ASSO). If you are upgrading from an older version of Smart IT where you have ASSO, you need to remove ASSO integration or upgrade to Remedy Single Sign-On to upgrade Smart IT successfully. For more information, see the following topics: Best practice: We recommend that you upgrade the RSSO webagents when Smart IT is upgraded. |
Changing AR server and database reference
You can change AR server reference in the SMT:Administration Console and CONFIGURATION_PARAMETER table to point to AR load balancer. During the upgrade if MyITInstalledConfiguration.xml is not updated with the load balancer, then Smart IT installer replaces entries in the SMT:Administration Console and CONFIGURATION_PARAMETER table as per the entries in the MyITInstalledConfiguration.xml file. For more information, see KA #000245563.
Stage 2: Upgrade Smart IT
| Task | Action | Additional information |
|---|---|---|
| 1 | Resolve issues indicated by the installer, if any. | Ensure that all the following pre-installation checks run by the installer are successful before proceeding with the installation:
The installation will not proceed if the pre-installation check detects inconsistencies in the required components. |
3 | Do not use Xming to install the Smart IT server, because it might not perform reliably during installation. Instead, use VNC, MobaXterm, or any other client. | |
| 4 | Verify the Smart IT server installation. | Verify whether the upgrade is successful. |
Stage 3: Review Smart IT configurations
After you upgrade, review the following configurations to make your system more robust, secure, and efficient.
| Task | Action | Additional information |
|---|---|---|
| 1 | Configuring Tomcat server | To provide communication security among applications, configure SSL for the Apache Tomcat server. If you enabled SSL as part of the installation , SSL is already configured. |
| 2 | The integration of Remedy Single Sign-On with Smart IT. Remedy Single Sign-On authentication applies to both the universal client and to mobile applications. When a user logs in to a mobile device, the user is prompted to enter the hostname and port. If the server has SSO enabled, the mobile client opens a browser to the SSO login page. The SSO server sets the SSO cookies after authentication on to the device browser. When the user relaunches the application, if the cookies are not expired, the mobile client displays the application. If the cookies are expired, the user is shown the login page again for authentication. | |
| 3 | Smart IT permissions | To give users access to Smart IT, assign them the required user permissions. |
| 4 | Login ID requirements for service requests in Smart IT | If your environment uses BMC Service Request Management, ensure that the People records for non-support staff include a login ID. Service requests cannot be submitted for a customer who has a People record with no login ID. Service requests cannot be submitted, because the Smart Recorder uses the login ID to show available service request templates for that person . |
| 5 | Enabling full text search | Full text search (FTS) is an optional feature that you can install with the Remedy AR System server. To use FTS with Smart IT, you must install Remedy Knowledge Management, even if you do not plan to create knowledge articles. To use the complete FTS capability, you must configure and enable the FTS feature. |
| 6 | Enabling SSL for Openfire chat server | Complete the procedure to enable a secure sockets layer (SSL) for the Openfire chat server that runs with Remedy with Smart IT (Smart IT). |
| 7 | Configuring security options for Smart IT | Limit the types of files that users can attach to Smart IT records. Update the content security policy to allow users to attach images from external sources to knowledge articles. If you have Openfire chat installed, edit the openfire/conf/cross-domain-policy.xml file to only allow access to data from a specific domain (or domains). |
| 8 | Configuring the reconciliation method for assets | The Sandbox Job Calls setting, was added to the AST:AppSettings form in Smart IT 1.5. This setting controls how reconciliation calls (requests) are processed for assets. |
Stage 4: Deploy Smart IT to users
| Task | Action | Additional information |
|---|---|---|
| 1 | (Optional) Perform the post-upgrade tasks. | NA |
| 2 | IT users access Smart IT Apple iOS and Google Android mobile clients, as well as through the universal client. The universal client provides access through a web browser. | |
| 3 | Rebranding Smart IT on the Universal Client | Optionally, modify the CSS as per the design of Smart IT 20.02, if you have done the rebranding for the UX console before upgrading Smart IT. |
Comments
Log in or register to comment.