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 |
|
Troubleshooting: Smart Analytics background schedule in SMIS
In Smart Analytics, some background processes are managed by Integration Manager, which is a plug-in based platform called Service Manager Integration Suite (SMIS). In the out-of-box system, Smart Analytics have three types of SMIS instances:
-
SMIDOL
The SMIDOL instance is for the training, testing, index, and tuning processes, which are triggered in Smart Analytics Configuration. Normally, one Service Manager server only has one SMIDOL instance named as SMIDOL*. The asterisk sign is the sequence number, which is usually 0.
-
SMIDOLOCR
The SMIDOLOCR instance is for the image analyzing process, which is triggered when users submit requests from the ESS portal (including SRC and the Mobility client). For performance consideration, you can have multiple SMIDOLOCR instances for one Service Manager server. The number of instances equals to the thread number of the Image Servers. If the Image Servers cannot be connected, only one instance is created. The instance name is SMIDOLOCR* (The asterisk is the sequence number). The Optical Character Recognition (OCR) task will be added to one of these instances after an interaction is created in ESS, depending on which instance has the least tasks in queue.
-
SMIDOLAutoFill
The SMIDOLAutoFill instance is for the auto-fill process. If an interaction is submitted to ESS without an attachment, a task will be added into this instance. In addition, if SMIDOLOCR is done, a SMIDOLAutoFill task will be also added . For performance consideration, one SM server has multiple SMIDOLAutoFill instances. The number of instances equals to the thread number of the IDOL Server. If the IDOL Server cannot be connected, only one instance will be created. The instance name is SMIDOLAutoFill* (The asterisk is the sequence number).
You can check the following topics on troubleshooting Smart Analytics background schedule in SMIS:
Manually create and enable an instance in SMIS
The SMIDOL and SMIDOLAutoFill instances are created and enabled automatically when you enable Smart Analytics in the Smart Analytics Configuration menu. The SMIDOLOCR is created and enabled automatically when you enable the Image Server in the Smart Analytics Configuration menu. These instances are also created when corresponding processes are triggered, such as the training, testing, tuning, index, or image process.
If the instance is not created automatically or you want do some troubleshooting, you can manually start up these SMIS instances for Smart Analytics.
To create and enable a SMIS instance for Smart Analytics manually, follow these steps:
-
Do one of the following to access Integration Manager:
- Click Tailoring > Integration Manager.
- Type smis in the command line, and then press Enter.
- Click Add.
- Select the SMIDOL , SMIDOLAutoFill, or SMIDOLOCR template, and then click Next. The Integration Instance Information screen is displayed.
- Change the configuration as needed, and then click Next. The Parameters screen is displayed.
- Do not change anything and click Next. The Fields screen is displayed.
- Do not change anything and click Next. The Mapping screen is displayed.
- Click Finish. The main SMIS configuration screen is displayed.
- Click Enable to enable the instance.
Manually disable and remove an instance in SMIS
The SMIDOL and SMIDOLAutoFill instances are removed when you disable Smart Analytics while the SMIDOLOCR instances are removed when you disable the Image Server in the Smart Analytics Configuration menu.
If you want to manually disable or delete an SMIS instance, follow these steps:
-
Do one of the following to access Integration Manager:
- Click Tailoring > Integration Manager.
- Type smis in the command line, and then press Enter.
- Select an instance, and then click Disable or Remove.
Configure the SMIS instances
If the SMIDOL, SMIDOLAutoFill, and SMIDOLOCR instances are created automatically, the default configuration is defined as follows:
| Name: |
SMIDOL*, SMIDOLAutoFill*, or SMIDOLOCR* Note The asterisk sign (*) is the sequence number starting from 0. |
| Interval Times: | 30s |
| Max Retry Times: | 5 |
| Log Level: | INFO |
| Log File Directory: | N/A |
| Run as system startup: | true |
To change the settings for performance tuning or troubleshooting, follow these steps:
-
Do one of the following to access Integration Manager:
- Click Tailoring > Integration Manager.
- Type smis in the command line, and then press Enter.
-
Select an instance, and then click Disable.
- Select the disabled instance, and then click Edit.
- Change the configuration, and then click Finish.
Check task logs in SMIS
To view all the task logs, click Tailoring > Integration Manager, and then click Log.
For training, testing, tuning, and index operations, check the log for the SMIDOL* instance to identify the corresponding task.
For image operation, you have to check all the SMIDOLOCR* instances to identify the corresponding task.
Tip
- Besides the task log, the program executed by SMIS prints log to
sm.logby default. You can define another file to print all SMIS logs by specifying the log file directory in the SMIS instance. - By default, if SMIS fails to execute a task after five retries, the task is set as expired and will never be triggered automatically. However, you can retry the task manually.
- If a SMIS instance is always running and obviously no background process of this instance is running, this instance may be dead due to some exception that cannot be caught. In this case, you cannot disable or delete the instance from the SMIS configuration page. The workaround is to kill the corresponding SMIS process from the Service Manager System Status page.
