Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

(ATS6-APP09) ELN configuration management with ADM


Published on

(ATS6-APP09) ELN configuration management with ADM
Starting with AELN 6.7, Accelrys ELN administrators have complete control over the timing and distribution of software updates to clients using Accelrys Deployment Manager (ADM). This session provides a quick overview, then dives deep into the technical aspects of ADM. Attendees will leave with a better understanding of how to use ADM to lower the costs associated with managing client updates.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

(ATS6-APP09) ELN configuration management with ADM

  1. 1. (ATS6-APP09) ELN ConfigurationManagement with ADMMike WilsonAdvisory Product ManagerPlatform Product
  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. Agenda• Introduction to Accelrys Deployment Manager (ADM)• ADM Use Cases– Assigning profiles to users– Modifying or creating a profile– Creating a package• ADM Workflows
  4. 4. Overview• Introduction toAccelrys Deployment Manager
  5. 5. Accelrys Deployment Manager (ADM) is a service that pushesAccelrys ELN software configurations to ELN clients• Minimize the locally installed software footprint– Single, small installation regardless of Accelrys ELN version– Small application loader that works with the ADM service• Lower the installation burden– Push configuration to user base– Push new clients to user base• Provide flexibility and control– Assign users to different configurations– Define rules to control deployment based on group membershipWhat Is Accelrys Deployment Manager?
  6. 6. • Minimal client footprint– Application launcher– Components requiringregistry changes– Client delivered from server• Administrators control thetiming and distribution ofsoftware updates– Configuration changes– New releasesAccelrys ELN Client DeploymentDownload• Sections• Accelrys ELN Application• Home Page• Notebook Explorer• Editors• Accelrys Draw• Accelrys ELN AdaptersInstall• Black Ice print driver• Accelrys Draw 4.0 SP1• Accelrys ELN LauncherAccelrys ELN Client
  7. 7. • How ADM Works– Users assigned toAccelrys ELN configs– On log-in, correctversion downloaded– If right version alreadythere, no download– Log-in occurs againstdownloaded/incumbentclient• Key terminology– Package• A collection of executablecode that is delivered as awhole– Profile• The configuration to beapplied to a package; and apointer to the package– Rule Set• A set of criteria that is usedto assign a profile to a userADM Overview
  8. 8. Deliver the Right Config at the Right TimeReleaseProfile- 6.8Pilot GroupRule SetReleaseProfile-
  9. 9. ADM Entity Details• Release Packages– All binaries required to log in to Notebook– All binaries not otherwise available from Vault– Pre-6.7 equivalent: An MSI file• Profiles– A pointer to a Package– All Notebook app-level configuration– Pre-6.7 equivalent: A Config file• Mapping Rules– Ordered rules– Map between Release Profiles and Users or Groups– Unambiguously maps each user to a single Release Profile– Pre-6.7 equivalent: Manual process
  10. 10. Offline Roaming CitrixStandard V6.8.0.704-Offline V6.8.0.704-Roaming V6.8.0.704-CitrixWithPerformanceLoggingV6.8.0.704-Offline-PerfLog V6.8.0.704-Roaming-PerfLog V6.8.0.704-Citrix-PerfLogWith DebugLoggingV6.8.0.704-Offline-Debug V6.8.0.704-Roaming-Debug V6.8.0.704-Citrix-DebugAccelrys ELN Profiles Default profile
  11. 11. • Installation defaults to Offline profile– Action is only required if a different profile is needed– See “Assigning Profiles” for more information• Accelrys ELN includes profiles for offline, roaming, andCitrix configurationsAccelrys ELN Client Deployment
  12. 12. Assign a ProfileWorking with ADM rules
  13. 13. Example Rule Set<?xml version="1.0" encoding="utf-8"?><Rules xmlns:xsi="V6.8.0.704-Roaming"><!-- SNIPPED: Help text --><Rule userSelector=Debug Logging profile=V6.8.0.704-Debug /><Rule userSelector=Citrix Users profile=V6.8.0.704-Citrix /></Rules>Key Elements– defaultProfile• Specifies the profile to be used if no rule applies to thecurrent user– userSelector• Maps a user or group to a profileADM Rule SetRule Processing– Rules are evaluated in order (top tobottom)– First match assigns profile– Default profile is assigned when no rulematches the user
  14. 14. To change the default profile to Roaming from Offline storage:• Download the ADM rule set– VaultADMStoreManager /vault <server> <user> <password> download-rulesc:ADMRulesrules.xml• Open the rules.xml file in a text editor– ChangedefaultProfile="V6.8.0.704-Offline"todefaultProfile="V6.8.0.704-Roaming"– Save the changes• Upload the changes to ADM– VaultADMStoreManager /vault <server> <user> <password> upload-rulesc:ADMRulesrules.xmlScenario: Change default profile to RoamingTip: Use Groups to assign profiles to minimize rule editing
  15. 15. Create/Update ProfilesEnable clone to latest feature for testing
  16. 16. • The client manager loads software based on the ADMprofile assigned to the current user• A profile specifies– Which software package to use– The application config file to use with that package• Except the <runtime> elements, which are extracted and stored with thepackage itselfProfile Composition
  17. 17. • In this example we will use an existing profile to create a new profile to enablethe Clone to Latest feature for use by a test group• Generate a working directory with the roaming profile– VaultADMStoreManager /vault <server> <user> <password> generate V6.8.0.704-Roamingc:MyProfile• Open the ELN application configuration file (in c:MyProfile) in a text editor– Change<add key="EnableCloneToLatest" value="false">to<add key="EnableCloneToLatest" value="true">– Save the changes• Upload the changes to ADM as a new profile– VaultADMStoreManager /vault <server> <user> <password> add-profileCloneToLatestProfile c:MyProfileScenario: Create a Profile
  18. 18. Create a PackageWorking with ADM PackagesExample: distribute the widgets from the widget buildingsession
  19. 19. • An ADM package is a collection of executable code that is intended tooperate together– Accelrys ELN releases are delivered in packages• Package creation should be a rare event – in most cases the standardrelease package will be sufficient• Customers can create packages that build on an Accelrys ELN releasewith the addition of custom code• Package size should be minimized by including only items that cannot bedelivered via the assembly cache– Non-.NET code– Unsigned codePackage Overview
  20. 20. • Process– Create/Use a key pair• VaultADMStoreManager create-key MyCorp.keypair– Extract the public key• VaultADMStoreManager get-public-key MyCorp.publickey– Set up a namespace on your test Vault server• VaultADMStoreManager /vault <server> <user> <password> add-namespaceMyCorpNameSpace MyCorp.publickey– Generate a working directory based on an existing profile• VaultADMStoreManager /vault <server> <user> <password> generate ExistingProfileC:WorkingDirectoryMyCorpPackage– Modify the working directory to meet your needs• Copy the widget assemblies to the working directory– Test the changes by executing Accelrys ELN from the working directoryPackage Creation
  21. 21. • Process, cont’d– Add the new package and profile to the test server• VaultADMStoreManager /vault <server> <user> <password> add-package NewProfileNameNamespace NewPackageName MyCorp.keypair C:WorkingDirectoryMyCorpPackage• Package will be created in test mode where it may be altered if needed– Modify the rule set to assign the profile to a test group/user– Test the new package from the server– (Optional) Update the package if changes are needed• VaultADMStoreManager /vault <server> <user> <password> update-packageMyCorpNamespace PackageName C:WorkingDirectoryMyCorpPackage MyCorp.keypair– Release the package• VaultADMStoreManager /vault <server> <user> <password> release MyCorpNamespaceMyCorpPackage• Preventing further alteration of the packagePackage Creation, cont’d
  22. 22. • VaultADMStoreManager can export packages and profiles for later import toanother ADM store– Export and import are typically used in promotion scenarios to transfer testedconfigurations from development to test to production• export-package– Exports a released package from an ADM store to a file for later import• export-profile– Exports a profile from an ADM store to a file for later import• import-package– Imports a package created by the export-package command• import-profile– Imports a profile created by the export-profile commandPromotion Commands
  23. 23. Summary• We reviewed the ELN client deployment manager and implemented common ITmanagement use cases using the VaultADMStoreManager utility– Assigned users to ELN configurations– Added an extension to the ELN configuration– Walked through the test/promotion lifecycle• Resources– Notebook IT/Admin forum on the Accelrys Community• Email to join– VaultADMStoreManager Command Glossary (attached to this presentation)• How to contact Accelrys Support– Email– Accelrys community (
  24. 24. Appendix• VaultADMStoreManager Commands & Usage
  25. 25. • VaultADMStoreManager is the command line utility thatmanages ADM entities (packages, profiles, rules)• ADM entities may be stored in– Vault: ADM stores are used to manage the software availablefor use with a Vault server– Local: ADM stores are used to develop new ADM packages andADM automation proceduresVaultADMStoreManager Overview
  26. 26. • Syntax– VaultADMStoreManager [/nostore | /local <store-folder> | /vault <server> <user> <password>]<command> <arguments>• Storage Options:– /nostore• Do not connect to a local or Vault store• Used for key-pair generation and folder status– /local <store-folder>• Use or create an ADM store in <store-folder>• Typically used to test ADM automation scripts or package construction without a Vault server– /vault <server> <user> <password>• Use the ADM store in the specified vault server and connect with the specified credentials• If <password> is an empty string (""), you will be prompted for your password on the command-line• Tip: use the /console command with the login to create an ADM console session– Eliminates the need to provide login credentials with each commandVaultADMStoreManager Syntax
  27. 27. • Rule Set– download-rules– upload-rules• Profiles– list-profiles– add-profile– update-profile– change-profile-package• Package Management– add-package– list-packages– release– update-package• Working Directories– generate– get-folder-status• Package Security– add-namespace– list-namespaces– create-key– get-public-key• Promotion– export-profile– import-profile– export-package– import-packageVaultADMStore Commands
  28. 28. • generate– Downloads an ADM profile and package to a working directory– Used to edit or create new profiles– Used to create new packages• get-folder-status– Displays the ADM properties of a given working directory• ADM store, package, profileGeneral Commands
  29. 29. • Rule Sets– download-rules• Downloads the rule set from an ADM store to a file– upload-rules• Uploads a file containing a rule set to an ADM store• Profiles– list-profiles• Lists the profiles present in an ADM store– add-profile• Adds a profile to an ADM store– update-profile• Updates an existing profile in an ADM store– change-profile-package• Changes the package used by a profileRule Set & Profile Commands
  30. 30. • ADM packages are used to define a software deployment that can be managedas an entity for delivery to clients• Package management commands– add-package• Adds a package to an ADM store• Packages are initially created in test mode and may be altered– Test mode packages are downloaded on each login and should only be used during development– update-package• Updates the specified package based on the working directory• Only test packages can be updated– list-packages• Lists the packages in an ADM store– release• Finalizes a package• No further changes can be made to the packagePackage Management Commands
  31. 31. • ADM packages must be signed and assigned a namespace for security and verificationpurposes– The namespace/key combination enables verification of the publisher• Key management commands– create-key• Creates a public/private key pair and writes them to a file• The key pair is used to sign packages– get-public-key• Extracts the public key from a key pair file created with create-key• The public key is used to verify packages and create namespaces• Namespace management commands– add-namespace• Creates a namespace in an ADM store and associates it with a public key• The namespace will only accept packages that have the correct namespace and public key– list-namespaces• Lists the namespaces in an ADM storePackage Security Commands
  32. 32. • VaultADMStoreManager can export packages and profiles for later import toanother ADM store– Export and import are typically used in promotion scenarios to transfer testedconfigurations from development to test to production• export-package– Exports a released package from an ADM store to a file for later import• export-profile– Exports a profile from an ADM store to a file for later import• import-package– Imports a package created by the export-package command• import-profile– Imports a profile created by the export-profile commandPromotion Commands