The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*
This guide provides a more detailed description of the syntax that is supported along with examples.
This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.
Concept Search - What can I type?
For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.
Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.
The setup_testbed system is made up of UNIX shell scripts, which can run under UNIX,
or under the BASH shell in Windows. The three types of scripts that comprise the
system are: a variables script (setup_testbed_vars.sh), a driver script
(setup_testbed.sh), and worker scripts (install_framework.sh, patch_tec.sh, etc).
The driver script calls the variables script to get a list of worker scripts to run, and then
runs the worker scripts, one at a time. The worker scripts do the actual product
install or patch. The worker scripts call the variables script to get the specific
variables needed to perform the function, such as the path to code to install, target
systems for installation, etc.
The driver script and worker scripts log messages, including standard error and
standard out, to a file in /tmp, whose name matches the name of the script, with a .log extension (ie, setup_testbed.log). If any errors occur, execution of the current
script ends, and no more worker scripts are run.
The steps to use the system are: 1)Edit the setup_testbed_vars.sh file. 2)Run the setup_testbed.sh script. 3)When complete, check the log files for errors. 4)If errors occur, fix the problem. 5)Rerun the setup_testbed.sh script.
If you only need to run 1 worker script, you can run it directly, instead of using the
The worker scripts included with this publication perform the following: install Tivoli