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

More documents

Recommendations

Info

Chapter 4: Analyzing ESB Artifacts in Archives, Stores, and File Systems Reporting on Impact Analysis An impact analysis report combines aspects of “Reporting Differences” and “Reporting on SonicMQ Reverse Dependencies.” Together, these features define the impact on the target store that would result from merging the source store into the target store. Because this report provides impact, the following information is also included: ● If a binary file type is different, the impact analysis report indicates that the file in the source store will overwrite the one in the target store. ● If a file exists in the source store but not in the target store, the impact analysis report indicates that a new file will be added to the target store. However, if a file exists in the target store but not in the source store, it is not reported, as it is not impacted and will not be affected by any import actions. ● If a dependency indicates that SonicMQ configuration objects must be created, the impact analysis report describes the requirement. Conversely, if existing SonicMQ configuration objects are no longer required by ESB, the impact analysis report notes that fact. (There might be non-ESB related references to a SonicMQ configuration.) The syntax of the impact command in the Sonic ESB Admin Tool is: impact -storeType storeParameters -storeType storeParameters [-out outputFile.xml] [-v] where: ■ The first -storeType storeParameters identifies the source artifact store, and the next -storeType storeParameters identifies the target artifact store. ■ storeType is { xar | fs | ds }. ■ storeParameters are: ❑ When storeType is xar, the archive location on a file system ❑ When storeType is fs, the root of the hierarchy on a file system ❑ When storeType is ds, the management connection to a domain in the form: domainName hostname:port [user password] ■ outputfile is the preferred target XML file name and location for the analysis report on the file system. When you do not specify this parameter, the output file is created as Sonic_ImpactAnalysis.xml in the tool’s directory. ■ -v requests verbose reporting (otherwise, you get terse reporting). Assessing impact on a Directory Service store requires a connect command to establish a connection to the domain prior to running impact. 102 Progress Sonic ESB Deployment Guide 8.5
Examples of the impact Commands ● Reporting the impact of a XAR on a Directory Service store: Reporting on Impact Analysis ESBAdmin> impact -xar sourceStore.xar -ds Domain1 myHost:2506 aUser aPassword ● Reporting the Impact of a file system on a XAR: ESBAdmin> impact -fs C:/myinstalldir/ESB -xar source.xar Progress Sonic ESB Deployment Guide 8.5 103
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: 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 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 152 and 153:
Chapter 8: Distributed Deployment a
Page 154 and 155:
Page 156 and 157:
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?