Broker 10.5 | webMethods Broker Documentation | webMethods Broker Messaging Programmer's Guide | webMethods Messaging Administration | JMSAdmin Command Reference | JMSAdmin Command Descriptions | Export
Creates a script file of JMSAdmin bind commands that will recreate the entries bound into JNDI.
export { ( * | lookup-name )+ } to { filename | stdout }
[ ( { append | overwrite } ) ]
The command syntax has these parts:
Required. The name used to look up the entry in the JNDI directory.
Required. The name of the command file that will be created, or whether the bind statements will be directed to the console.
Optional. The append parameter to add the results of the command to the end of the named file, if it exists. If the specified file does not exist, a new file will be created.
If you use the overwrite option and the specified file currently exists, the existing data in the file will be replaced with new data. If the file exists and you do not specify overwrite, JMSAdmin will issue an error.
You can export all entries within a context or individual entries.
The export file contains a bind statement for each webMethods administered object in the specified context (only webMethods administered objects are exported). You can export to a file or to stdout. Exporting to stdout is most useful when it is redirected at JMSAdmin startup.
Only JNDI bind commands can be exported to a script file. If the commands are exported to a file rather than stdout, you can edit the script file (for example, to add commands) before executing the file, if desired.
When you specify filename in Windows notation, which uses the backslash character (\) as the directory separator, you must enclose the entire pathname in quotes.
The following example creates bind statements for all connection factories, queues, and topics in the context /Production/HR and saves them in the file, HR_Prod_Def.txt:
\> export /Production/HR to myData/exports/HR_Prod_Def.txt (UNIX)
\> export /Production/HR to "myData\exports\HR_Prod_Def.txt" (Windows)
The first statement below switches to the /Test/Manufacturing context, and the second statement exports all webMethods Broker objects in that context and stores them in the file TestEnvironment.txt:
\> cd /Test/Manufacturing
\> export * to TestEnvironment.txt
The following example exports two objects (NewMachineTopic and OldMachineTopic) in the Test context and appends them to TestEnvironment.txt:
> export /Test/NewMachineTopic /Test/OldMachineTopic to
TestEnvironment.txt (append)
Related Commands