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 |
|
Command Line tool
Application Deployment provides a command line tool to help you import and export application deployment data. It has the following syntax:
/opt/opsware/da/bin/admtool.sh -opType [--appListTypeappList|appListFile] --fileTypefilePath [--importConflict overwrite|skip]
You can use this tool to import or export all the applications or a subset thereof.
|
Option |
Description |
|---|---|
|
opType |
Specifies the operation: You can abbreviate this option by specifying |
|
appListType |
Optional: Indicates that specific applications will be imported or exported and how the application names will be specified:
If you do not specify this option, all applications are imported or exported. |
|
appList |
List of applications that will be imported or exported. Application names must be separated with semicolons:
Used only with the |
|
appListFile |
CSV file containing the list of applications that will be imported or exported. Application names must be separated with semicolons:
Used only with the |
|
fileType |
Specify Specify |
|
filePath |
Full path and name of the XML file to import to, export from, or preview. If you do not specify a file name for an export operation, a default export file is used. You can specify the default export file in the
If |
|
|
Optional: Indicates what happens if a conflict occurs during an import operation:
You can abbreviate this option by specifying |
Syntax examples
The following tables show the correct syntax for each type of import and export scenario that the Application Deployment Manager supports.
|
Preview scenario |
Example |
|---|---|
|
Full Import Preview (all applications in the specified XML file) |
|
|
Full Import Preview with Overwrite on Conflict |
|
|
Partial Import Preview of Specific Applications (listed on the command line) |
|
|
Partial Import Preview of Specific Applications (listed on the command line) with Overwrite on Conflict |
|
|
Partial Import Preview of Specific Applications (listed in a CSV file) |
|
|
Partial Import Preview of Specific Applications (listed in a CSV file) with Overwrite on Conflict |
|
See Preview examples for additional information.
|
Import scenario |
Example |
|---|---|
|
Full Import (all applications in the specified XML file) |
|
|
Full Import with Overwrite on Conflict |
|
|
Partial Import of Specific Applications (listed on the command line) |
|
|
Partial Import of Specific Applications (listed on the command line) with Overwrite on Conflict |
|
|
Partial Import of Specific Applications (listed in a CSV file) |
|
|
Partial Import of Specific Applications (listed in a CSV file) with Overwrite on Conflict |
|
See Import examples for additional information.
|
Export scenario |
Example |
|---|---|
|
Full Export of All Application Deployment Data |
|
|
Partial Export of Specific Applications (listed on the command line) |
|
|
Partial Export of Specific Applications (listed in a CSV file)s |
|
See Export examples for additional information.
In these examples, the app_list.csv file contains a list of application names separated by semicolons (;). For example: app1;app2;app3;app4
Overwrite conflict resolution
A conflict occurs when an item in the import XML file already exists in the Application Deployment database on this SA core. By default, the conflicted item is skipped during the import.
If you specify the --importConflict overwrite option, however, the conflicted item is modified instead. Certain items associated with a specific release can also be deleted.
The following table summarizes the results of an import operation when --importConflict overwrite is specified.
|
Type of item |
In import file |
In import file |
Not in import file |
|---|---|---|---|
|
Application Application group Release associated with a specific application Environment Lifecycle Tier Tier group Script Source type |
Item is created |
Item is updated based on the content of the import file |
Item remains in the database and is not modified |
|
Tier associated with a specific release Component associated with a tier that is associated with a specific release |
Item is created |
Item is updated based on the content of the import file |
Item is deleted |
See Messages regarding data conflicts under Important messages for examples of messages that pertain to import conflicts.
Log files
The admtool.sh tool produces a detailed log file. The file name depends on the operation performed:
/var/log/opsware/da/importData.log
/var/log/opsware/da/exportData.log
/var/log/opsware/da/previewData.log
Important messages
For a preview operation, the following type of message (on stdout) indicates that something new will be created if this import is performed:
Import: 'CodeComponentSourceType' 'QA' will be created.
The following type of message indicates that an application will be skipped because it was not included in the list of applications to be imported or exported:
Skip: Application 'AppD' due to Application Filter.
For an import operation, the following type of message (on stdout) indicates that a library item—such as a Software Policy, Package, or Application Configuration—does not exist on the destination SA core:
Not Found:Package'OPSWpytwist2-40.0.0.7.325.zip(SunOS 5.8)'does not exist
The following types of messages indicate whether a conflict exists between the existing Application Deployment data on the destination SA core and the data in the import XML file:
|
Mode |
Conflict Resolution |
Conflict Detected? |
Sample Message |
|---|---|---|---|
|
Preview |
Overwrite |
Yes |
|
|
Preview |
Skip |
Yes |
Conflict: Release 'App1:Release1' already exists. will skip. |
|
Preview |
Overwrite or Skip |
No |
|
|
Import |
Overwrite |
Yes |
|
|
Import |
Overwrite |
Yes |
|
|
Import |
Skip |
Yes |
|
|
Import |
Overwrite or Skip |
No |
|
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 hpe_sa_docs@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: