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.
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. |
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 |
|
- Create Jython Code
- Use External Java JAR Files within Jython
- Execution of the Code
- Modifying Out-of-the-Box Scripts
- Structure of the Jython File
- Results Generation by the Jython Script
- The Framework Instance
- Finding the Correct Credentials (for Connection Adapters)
- Handling Exceptions from Java
- Troubleshooting Migration from Jython Version 2.1 to 2.5.3
Modifying Out-of-the-Box Scripts
When making out-of-the-box script modifications, make only minimal changes to the script and place any necessary methods in an external script. You can track changes more efficiently and, when moving to a newer
For example, the following single line of code in an out-of-the-box script calls a method that calculates a Web server name in an application-specific way:
serverName = iplanet_cspecific.PlugInProcessing(serverName, transportHN, mam_utils)
The more complex logic that decides how to calculate this name is contained in an external script:
# implement customer specific processing for 'servername' attribute of httpplugin # def PlugInProcessing(servername, transportHN, mam_utils_handle): # support application-specific HTTP plug-in naming if servername == "appsrv_instance": # servername is supposed to match up with the j2ee server name, however some groups do strange things with their # iPlanet plug-in files. this is the best work-around we could find. this join can't be done with IP address:port # because multiple apps on a web server share the same IP:port for multiple websphere applications logger.debug('httpcontext_webapplicationserver attribute has been changed from [' + servername + '] to [' + transportHN[:5] + '] to facilitate websphere enrichment') servername = transportHN[:5] return servername
Save the external script in the External Resources folder. For details, see Resources Pane. If you add this script to a package, you can use this script for other jobs, too. For details on working with Package Manager, see Package Manager.
During upgrade, the change you make to the single line of code is overwritten by the new version of the out-of-the-box script, so you will need to replace the line. However, the external script is not overwritten.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: