esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

More documents

Recommendations

Info

Chapter 5: Importing Deployment Artifacts into a Domain Importing or Merging ESB Artifacts With the ESB Admin Tool The Sonic ESB command line tool, ESB Admin Too, adds ESB artifacts in a Sonic Archive or a file store to a target domain. Note See the “Sonic ESB Tools and Samples” chapter of the Progress Sonic ESB Configuration and Management Guide for more information on this tool. Starting the ESB Admin Tool On the system where you will run the import process, start the ESB Admin Tool: ● Under Windows, choose: Start > Programs > Progress > Sonic 8.5 > Tools > ESB Admin Tool ● Under UNIX or Linux, on a system installed with the Sonic ESB Administration Tools, open a console window to the Sonic ESB installation directory, and enter: ./bin/esbadmin.sh The ESB Admin Tool opens. For a list of commands, enter: ESBAdmin> help (or ?). Connecting to the Target Domain All import actions require that you open the archive and then establish connection to the target domain. Enter the connection data for the domain using the syntax: connect domain url [username] [password] [managementNode] For example: ESBAdmin> connect Domain1 localhost:2506 Administrator Administrator Using Import Properties When you use the Deployment Import Tool, the rules you define to overwrite or ignore specified files or folders can be saved. (See “Saving a Deployment Import Property File” on page 111). That file can be used on subsequent imports with either the Deployment Import Tool or the ESB Admin Tool import commands. You can edit an import properties file. Start with an existing rules file that has some ignore and some overwrite settings to observe the syntax of the import properties. 116 Progress Sonic ESB Deployment Guide 8.5
Using the Import Archive Command Importing or Merging ESB Artifacts With the ESB Admin Tool The import archive command syntax reads an archive file, and, optionally, a related import properties file in its command line: ESBAdmin> import archive source.xar [import_prop.xml | override ] where: ■ souce.xar is the path and name of the file (using the .xar extension) of the deployment archive package to be imported. ■ One of the following arguments is used: ❑ import-prop.xml — When an appropriate import properties file exists, you can use its location as a parameter of the command to apply the defined overwrite and ignore settings. ❑ override — Import everything in the archive file with overwrite set to true. As an example, you might import the RIA export archive and use the defined import properties file (when the archive and the import properties file are at the ESB installation root) as: ESBAdmin> import archive C:\RIA_DIT.xar C:\RIA_DIT_Import.xml Using the Import FS Command When the source store is a file store, use the import fs command.Its syntax reads a file system structure, and, optionally, a related import properties file in its command line: ESBAdmin> import fs sourceFileStore [import_prop.xml | override ] where: ■ sourceFileStore is the root of the file system hierarchy that contains the files to be imported into the connected Directory Service’s store. ■ One of the following arguments is used: ❑ import-prop.xml — When an import properties file exists, it can be applied as a parameter of the command to apply the defined overwrite and ignore settings. ❑ override — Import everything in the file system file with overwrite set to true. Progress Sonic ESB Deployment Guide 8.5 117
Page 1 and 2:
® ® PROGRESS® SONIC® Sonic ESB
Page 3 and 4:
the redistribution, if any, must in
Page 5 and 6:
the relevant code modules. All Righ
Page 7 and 8:
OF USE, DATA, OR PROFITS; OR BUSINE
Page 9:
products derived from this software
Page 12 and 13:
Contents Using the Deployment Expor
Page 14 and 15:
Contents Chapter 7: Updating a Revi
Page 16 and 17:
Preface About This Guide This guide
Page 18 and 19:
Preface Progress Sonic Documentatio
Page 20 and 21:
Preface 20 Progress Sonic ESB Deplo
Page 22 and 23:
Chapter 1: Introduction Roles in Re
Page 24 and 25:
Chapter 1: Introduction Developing
Page 26 and 27:
Chapter 1: Introduction ESB Artifac
Page 28 and 29:
Chapter 1: Introduction Different P
Page 30 and 31:
Chapter 1: Introduction 30 Progress
Page 32 and 33:
Chapter 2: Exporting ESB Artifacts
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Chapter 3: Mapping ESB Artifacts to
Page 62 and 63:
Page 64 and 65:
Page 66 and 67: Chapter 3: Mapping ESB Artifacts to
Page 96 and 97: Chapter 4: Analyzing ESB Artifacts
Page 106 and 107: Chapter 5: Importing Deployment Art
Page 122 and 123: Chapter 6: Adapting Imported Servic
Page 140 and 141: Chapter 7: Updating a Revised Deplo
Page 146 and 147: Chapter 8: Distributed Deployment a
Page 162 and 163: Index ESBWS WSDL files external to
Page 164: Index 164 Progress Sonic ESB Deploy
show all

esb_deploy - Progress Sonic ESB Deployment Guide 8.5 - Product ...

Create successful ePaper yourself

Delete template?

Save as template?