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

More documents

Recommendations

Info

Chapter 5: Importing Deployment Artifacts into a Domain Overview The deployment import process is based on the existence of target domains and deployment files extracted from source Workbench or deployment domains. The “Mapping ESB Artifacts to Target Domains” chapters described different ways to set up staging, source control, mapping of archives to target domains, and Directory Service population. This chapter discusses the procedures that take a mapped archive (or unmapped export files in a file store) and import it into the target domain. In this chapter, you see how the Sonic Deployment Archive Import Tool helps you create import rules to determine which files to overwrite and which to ignore. After developing import rules, the import process can be scripted, as described in “Defining Scripts to Automate Deployment” on page 81. The “Adapting Imported Services to a Domain” and “Updating a Revised Deployment” chapters discuss the final tuning of the imported ESB elements into the target domain, and the recurrence of the lifecycle when changes in developed applications are ready to update their previous deployment artifacts through established processes. Backing Up the Domain and Documenting Tests While importing deployment elements into an existing domain is not difficult, be sure you can recover the directory service if the updated domain is not accepted. Preparing a domain for import requires you to either stop and backup (incremental technique), or restore (build technique) the existing Directory Service. See “Incrementally Updating or Building Domains” on page 83 for more on these strategies. When you complete the backup or restoration of the Directory Service, start the container that hosts the Directory Service and the management broker. Developers should describe the tests (written as ESB services or processes) that verify their deployment elements when their work moves from Sonic Workbench into a target environment. Those tests can be added to the project elements packaged with the runtime deployment files. If regression or error conditions cannot be resolved, stop the domain manager and restore the directory service backup. 106 Progress Sonic ESB Deployment Guide 8.5
Using The Deployment Archive Import Tool Using The Deployment Archive Import Tool The Sonic Deployment Import Tool, when connected to a target domain manager, inserts selected configuration elements that are in a deployment archive or file store created by the Sonic Deployment Export Tool. Import properties files define rules to filter incoming elements. You can ignore some files and, for other files, specify that the imported file overwrite an existing file of the same identity. Importing elements from archive files involves: ● Defining import rules for the archive contents ● Updating the selected domain and reviewing logs of actions taken ◆ To start the Deployment Import Tool A system must have SonicMQ and Sonic ESB Administration Tools installed (these are included in the Sonic Workbench) to run this tool. 1. Check that the target domain manager is running. 2. On the system where you will administrate the import process, start the Sonic Deployment Import Tool: ■ Under Windows, choose Start > Programs > Progress > Sonic 8.5 > Tools > ESB Deployment Import 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 then enter: ./bin/deployImport.sh Setting Import Properties for ESB Artifacts into a Domain The Deployment Export Tool lets you select structures of files for inclusion in an export package. You could not, however, at the time of the export, select which dependent files would be allowed into the target domain and, for those files that are allowed in, which should overwrite existing files of the same name and location. That functionality is defined in import properties—notation of files and branches that should overwrite existing files and files that should be ignored. If you choose not to define import properties, the default behavior is assumed—all files in the ESB artifact store are imported but no imported file will overwrite an existing file. Note The Remote Information access export file that was mapped for the Developer Integration Testing (DIT) named RIA_DIT.xar after it was mapped is described in these procedures. Progress Sonic ESB Deployment Guide 8.5 107
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: Chapter 2: Exporting ESB Artifacts
Page 58 and 59: Chapter 2: Exporting ESB Artifacts
Page 60 and 61: Chapter 3: Mapping ESB Artifacts to
Page 96 and 97: Chapter 4: Analyzing ESB Artifacts
Page 108 and 109: 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 156 and 157:
Chapter 8: Distributed Deployment a
Page 158 and 159:
Page 160 and 161:
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?