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 |
|
- Publishing Service Manager data using WS API
- Things to consider prior to publishing data
- List: Web Services available in the Service Manager Web Services API
- Field names in the extaccess record
- Create dedicated Web Services listeners
- Data conversion between Service Manager and SOAP Web Services
- Example: Publishing the Terminate Change functionality via Web Services
- Publish a table as a Web service
- Expose a table with more than one web service
- Remove a Document Engine display action from the Web Services API
- Remove a Service Manager field from the Web Services API
- Sample client for Web Services SM7 URL
- Command line arguments for the Axis2 sample application
- Add an external access action to the Web Services
Create dedicated Web Services listeners
An Service Manager system configured for vertical or horizontal scaling uses a Load Balancer to redirect client connection requests to an available Service Manager process. A system that also has many Web Services may need a Load Balancer for multiple nodes. Service Manager's Web Services do not support http redirect, and will fail to clean up the resources on the Service Manager loadBalancer process, if the loadBalancer port is used as the endpoint URL. For this reason, we recommend creating one or more Service Manager processes dedicated to Web Services requests. You can then configure any external Web service clients to connect directly to the dedicated Service Manager processes. If your system needs a load balancer, use a hardware load balancer to balance between a set of servlets with the debugnode parameter.
- Log in to the host running Service Manager with an administrator account.
-
Stop the Service Manager server.
Note It is not necessary to stop and start the Service Manager server to add a new port. You can add the line to the
sm.cfgfile while the system is running and start that same port from a command prompt manually. -
Open the sm.cfg file, and create a dedicated Service Manager process to listen for Web Services requests using the -debugnode parameter. For example, the following entries create a dedicated process listening on ports 13085 and 13445.
sm -httpPort:13080 -loadbalancer
sm -httpPort:13081 -httpsPort:13443
sm -httpPort:13083 -httpsPort:13444
sm -httpPort:13085 -httpsPort:13445 -debugnode
Note The debugnode parameter tells the Service Manager Load Balancer not to forward any client connection requests to this Service Manager process. Only clients that directly connect to the process can access it.
- Restart the Service Manager server.
- Configure any external web service clients to connect directly to the Service Manager processes running in debugnode. For example, set the endpoint URL to http://<fully qualified host name>:13085/SM/7/<Service Name> for normal connections and set the URL to https://<fully qualified host name>:13445/SM/7/<Service Name> for SSL-encrypted connections.
