(ATS3-PLAT03) Enterprise Protocol &       Package Deployment                                             Jarek Tomczak    ...
The information on the roadmap and future software development efforts areintended to outline general product direction an...
Outline• Application Deployment• Deployment of Components and Protocols• Packaging and Package Deployment   –   When to us...
AEP Application Deployment  Develop    and         Test      Validate   Install        Test         Use Document          ...
Application Deployment – Bigger Picture         Release                                                                   ...
Deployment of Individual Components and ProtocolsDon’t do it!Potential issues:• Relationship to other application protocol...
Deployment of Individual Protocols• If you do then   – Enforce protocol validation   – Resources contained within the prot...
Packages• The only official way of  distributing Pipeline Pilot  collections• Fundamental unit of the AEP  ecosystem
Is Packaging Really Relevant?Number of package-related questions on the AccelrysPipeline Pilot Community forum…
When Packages Are• Necessary   – Custom Java/.NET components   – CGI scripts   – Executable files• Recommended   – Nearly ...
Benefits of Packaging•   A way of organising code•   Straightforward deployment to multiple servers•   Dependency manageme...
Benefits of Packaging cont.• Authorization    – Integration with Admin Portal•   Support for CGI scripts•   Handling of ex...
Packaging Issues• Need access to server for package development and  deployment• Cannot save packaged components/protocols...
Package Content and Directory Structure•   Components and protocols•   Configuration files•   Documentation•   Data files ...
Packaging Overview• Create a new package  perl mktree.pl --company=mycorp --product=myapp• Fix folder structure• Edit pack...
package.conf as Deployment Descriptor File  Identification   Dependency   Configuration     Testing     Documentation and ...
Apache HTTP Server Configuration• Deploy a web application to e.g.  http://server:9944/myapp• Deploy a custom Web / REST /...
Apache HTTP Server Configuration Options• Edit httpd.conf• Use documented package web directive   Web    myapp        $(pa...
Sending Specific MIME Type Files• Export of DICOM images• .dcm extension is not enough• HTTP header field:   Content-Type:...
Package-Defined Global Protocol Properties<PACKAGE_DIR>/package.conf
Application Role Management<PACKAGE_DIR>/xml/Objects/AuthzRegistry.xml Client has to provide corresponding clientType (in ...
Auto Parameters<PACKAGE_DIR>/xml/Objects/AutoParameters.xml<PACKAGE_DIR>/package.conf • complib • <autoparameters>
Light Relief & A Serious Issue                                 Would you plz be so kind                                 as...
Limited Access to PP Server…There is always Pipeline Pilot Professional Client or Web Port
Summary• Packages are the basic deployment unit and…•   There is even more: File Reader extensions, embedded packages…•   ...
The information on the roadmap and future software development efforts areintended to outline general product direction an...
Upcoming SlideShare
Loading in …5
×

(ATS3-PLAT03) Enterprise Protocol & Package Deployment

1,322 views

Published on

There is a significant difference between publication of individual protocols and deployment of complex applications consisting of a significant number of protocols combined with a custom Web interface and custom components developed in third party languages. This session will summarize existing methods of protocol deployment and then focus on various aspects of packaging and meta-packaging (on-fly package creation and installation) to address typical requirements of enterprise application publication like dependency management, configuration injection, security, application initialization, testing and continuous integration.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,322
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

(ATS3-PLAT03) Enterprise Protocol & Package Deployment

  1. 1. (ATS3-PLAT03) Enterprise Protocol & Package Deployment Jarek Tomczak Principal Solutions Architect, Professional Services Jaroslaw.Tomczak@accelrys.com
  2. 2. The information on the roadmap and future software development efforts areintended to outline general product direction and should not be relied on in makinga purchasing decision.
  3. 3. Outline• Application Deployment• Deployment of Components and Protocols• Packaging and Package Deployment – When to use – Benefits – Issues – Usage – Undocumented features
  4. 4. AEP Application Deployment Develop and Test Validate Install Test Use Document Development Test/Production
  5. 5. Application Deployment – Bigger Picture Release De-Release Package Advertise Advertise Retire A Characterization Framework for Software Deployment Technologies Antonio Carzaniga et al., 1998 Install De-Install Transfer Configure Update Adapt Transfer Configure Activate De-Activate
  6. 6. Deployment of Individual Components and ProtocolsDon’t do it!Potential issues:• Relationship to other application protocols• Dependent components• Additional resources, data etc.• Configuration management• Documentation
  7. 7. Deployment of Individual Protocols• If you do then – Enforce protocol validation – Resources contained within the protocol – Document manual deployment workflow• Actual deployment – Import/Export – Network tab
  8. 8. Packages• The only official way of distributing Pipeline Pilot collections• Fundamental unit of the AEP ecosystem
  9. 9. Is Packaging Really Relevant?Number of package-related questions on the AccelrysPipeline Pilot Community forum…
  10. 10. When Packages Are• Necessary – Custom Java/.NET components – CGI scripts – Executable files• Recommended – Nearly always
  11. 11. Benefits of Packaging• A way of organising code• Straightforward deployment to multiple servers• Dependency management• Configuration management – Package variables• Documentation (components, custom/API) – Integration with Help Center• Apache configuration
  12. 12. Benefits of Packaging cont.• Authorization – Integration with Admin Portal• Support for CGI scripts• Handling of executable files• Locked code• Versioning• Integrity check
  13. 13. Packaging Issues• Need access to server for package development and deployment• Cannot save packaged components/protocols (export) – Lost PP versioning through export/import• Tricky to use with SCM systems
  14. 14. Package Content and Directory Structure• Components and protocols• Configuration files• Documentation• Data files – Required by individual components/protocols – Baseline files for regression tests• Custom (Java, .NET etc.) components• Other code (e.g. Web applications)• Executable files
  15. 15. Packaging Overview• Create a new package perl mktree.pl --company=mycorp --product=myapp• Fix folder structure• Edit package.conf• Develop package components• Install (activate) the package (pkgutil -i)• Check integrity, validate GUIDs (pkgutil -q/-v)• Create zip file (pkgutil -buildpackagezip)
  16. 16. package.conf as Deployment Descriptor File Identification Dependency Configuration Testing Documentation and Versioning Management Global Test HelpDoc Vendor Require Web OnInstall Name OnUninstall Code Version Management Xml Data DotNet Java Perl
  17. 17. Apache HTTP Server Configuration• Deploy a web application to e.g. http://server:9944/myapp• Deploy a custom Web / REST / CGI service• Make a data directory browsable• Make a private directory non-browsable• Change default cache ages for images• …
  18. 18. Apache HTTP Server Configuration Options• Edit httpd.conf• Use documented package web directive Web myapp $(package)/web Web myapp-temp C:/Temp/myapp• Use undocumented package directives <web custom> insert ... </web>• Use a dedicated config file
  19. 19. Sending Specific MIME Type Files• Export of DICOM images• .dcm extension is not enough• HTTP header field: Content-Type: application/dicom• CGI Script<web custom>insert Alias /mime/getfile "C:/Program Files/Accelrys/PPS85/apps/accelrys/mime/bin/getfile.cgi"insert <Directory "C:/Program Files/Accelrys/PPS85/apps/accelrys/mime/bin">insert Options +ExecCGI -Indexes -IncludesNoExecinsert AllowOverride Noneinsert Order allow,denyinsert Allow from allinsert AddHandler cgi-script cgiinsert </Directory></web>
  20. 20. Package-Defined Global Protocol Properties<PACKAGE_DIR>/package.conf
  21. 21. Application Role Management<PACKAGE_DIR>/xml/Objects/AuthzRegistry.xml Client has to provide corresponding clientType (in PipelinePilotServer)
  22. 22. Auto Parameters<PACKAGE_DIR>/xml/Objects/AutoParameters.xml<PACKAGE_DIR>/package.conf • complib • <autoparameters>
  23. 23. Light Relief & A Serious Issue Would you plz be so kind as to send me the ordering details for your book “Pipeline Pilot for Dummies 2010?” I was unable to locate it on amazon… For Everyone
  24. 24. Limited Access to PP Server…There is always Pipeline Pilot Professional Client or Web Port
  25. 25. Summary• Packages are the basic deployment unit and…• There is even more: File Reader extensions, embedded packages…• Documentation is pretty good• But one can learn still from the “scitegic” package masters…• Relevant sessions – Web Development with Accelrys Enterprise Platform (ATS3-DEV06) – Team Development with Accelrys Enterprise Platform (ATS3-DEV08)
  26. 26. The information on the roadmap and future software development efforts areintended to outline general product direction and should not be relied on in makinga purchasing decision.For more information on the Accelrys Tech Summits and other IT & Developer information,please visit:https://community.accelrys.com/groups/it-dev

×