Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Creating and applying the production patch
Once you have handled all objects requiring reconciliation, you will create a tailored production patch and apply it to your actual production system. This chapter explains what you need to do to create a production patch and apply it to your tailored production Service Manager system.
Creating the production patch
Once you are satisfied with the results of your reconciliation process, you can create a production patch.
Note It is recommended that you back up your database after reconciling differences to prevent unexpected data loss.
Follow these steps to create the production patch:
- From the Windows client, log in to your Service Manager server as a System Administrator.
-
(Optional) You may need to exclude certain records on the production system from being built to the custom upgrade package. To do so, follow these steps:
- Click Tailoring > Differential Upgrade > Patch Records to open the Patch Maintenance page.
- Select APM from the drop-down list, and then press Enter.
- You can update the query definition as required.
- Save your changes.
-
Go to System Administration > Ongoing Maintenance > Upgrade Utility > Create Custom Upgrade.
The Applications Patch Manager asks you to prepare an area to contain the applications patch files that you will create. This can be referred to as the production patch directory.
- Using the standard method for your operating system, create the production patch directory.
- Enter a path in the production patch directory. This path must point to a location that the server can access.
-
Click Next.
The Applications Patch Manager displays the version you will create the patch for.
-
Click Next to create the patch.
The Applications Patch Manager creates the production patch in the Applications Patch Manager production patch directory.
After you test this patch and confirm that it works as desired, you will be able to apply it to your production system.
Testing the production patch
After creating the applications patch for your production system, test it extensively. This will be an iterative process that may require several changes to patch objects and the recreation of production patches. Employ user acceptance testing verification and validate your changes.
Applying the production patch
The steps that you used to apply the out-of-box patch to the copy of your production system are the same steps you need to apply to the production patch that you created in your actual production system.
Note When applying the patch to the production system, you must be the only user logged in to the system.
Follow these steps to apply the patch you created to your production system:
- Have all users log out of the server.
-
Prevent users from logging into your Service Manager server by running the quiesce command from the operating system’s command prompt.
sm -quiesce:1
- Open the sm.ini file. By default, the file is located on the Service Manager server in the C:\Program Files (x86)\Micro Focus\Service Manager\Server\RUN folder.
- Add
sessiontimeout:60andir_disable:1to this file, and then save your changes. - From the Windows client, use the English language to log on to your Service Manager server as a System Administrator.
-
Go to System Administration > Ongoing Maintenance > Upgrade Utility > Apply Upgrade.
Service Manager displays a screen that asks you to input the fully qualified path to the production patch.
-
Enter the fully qualified path of the production patch directory, and then click Next. The path must be relative to the server, instead of to the client computer, if the client is not installed on the same machine as the server.
The Applications Patch Manager displays the current version of your applications and the version that will result after you apply the patch.
-
Confirm that the source and target versions listed match your current production system and the applications patch version, and then click Next to apply the patch.
When the Applications Patch Manager finishes applying the patch, it displays a message indicating that your system was successfully updated.
- Click Finish.
- Log out from your Service Manager server, and then log in again.
-
Allow users to log in to the server by running the sm -quiesce:0 command from the operating system’s command prompt.
- Restart the Service Manager server.
Going live after applying the production patch
Any tailored objects that were updated by the application patch are backed up as a revision. If issues are encountered after going live, these objects can be quickly swapped back to their original tailored versions. After a period of time, you may want to delete the old revision objects.
