(ATS6-PLAT07) Managing AEP in an enterprise environment

616 views

Published on

Accelrys Enterprise Platform use within an Enterprise environment spans from Power users of Pipeline Pilot to web applications and High Performance Computing. Managing the balance between productivity and enterprise policies can be tricky. This session will focus on exposing the tools and processes needed by administrators to enable users to be productive, yet allowing IT to remain in control.

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
616
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

(ATS6-PLAT07) Managing AEP in an enterprise environment

  1. 1. (ATS6-PLAT07) Managing AEP in anEnterprise EnvironmentConrad AgramontSenior Product Manager, Enterprise TechnologiesAccelrys Enterprise Platformconrad.Agramont@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. Content• Deployments• Folders• Tools
  4. 4. Deployments• Spectrum of deployments• Installer
  5. 5. Laptop/Desktop Workgroup Enterprise Cloud HPCKey Benefit Personal Productivity Collaboration Applications &ManagementFlexibility PerformanceManaged by Scientific User Team/Application Admin IT + Application Admin Scientific User/Vendor HPC ITDeployment One install, works outof the boxSome customization, 1-few serversMany ServersWeb FarmCloud Vendor Grid Schedulers,specialized hardwareConfiguration None to simple Simple Flexible and Complete Complete CompleteSecurity: Authentication File and ActiveDirectoryActive Directory Active Directory, SAML,KerberosLocal CredentialSAML/OAuthLDAP/Kerberos/PAMService Level Agreement N/A N/A Business Operations Cloud Vendor Business OperationsSpectrum of DeploymentsCustomer Choice
  6. 6. Walking through the installer
  7. 7. • Install AEP without the GUI– Meant for the IT Admin– Not for the “Casual” scientificuser• Great for predictable,repeatable, and automatedinstallations– Testing– Additional Web Nodes• Details in Installation Guide"$MEDIADIR/bin/installcmdline" -execute -d$ROOT -l /tmp/license -p 9944 -s 9943 -c 1 -mSCITEGICMUTEXES -mode FirstTimeInstall -piscitegic/admin -pi scitegic/adminportal -piscitegic/appcatlog -pi scitegic/clientsdk -piscitegic/clientsdkdotnet -pi scitegic/clientsdkjava-pi scitegic/clientsdkjavascript -pi scitegic/core -piscitegic/coreutils -pi scitegic/dataaccess -piscitegic/docs -pi scitegic/dsbuilder -piscitegic/gems -pi scitegic/gemsapp -piscitegic/generic -pi scitegic/integration -piscitegic/javaserver -pi scitegic/launcher -piscitegic/mongodb -pi scitegic/queryservice -piscitegic/report -pi scitegic/reportadv -piscitegic/rss -pi scitegic/scheduler -piscitegic/sharepoint -pi scitegic/waf -piscitegic/web -pi scitegic/websvcUnattended Installation
  8. 8. HPCAEP Deployment MixologyWebProductionStagingAuthoringPersonal ProductivityCollaborationEnterprise Development
  9. 9. HPCEnterprise Deployment: It’s EverywhereWeb1000Scientists10Scientists10Scientists1AEP AdminWeb750Scientists10Scientists2AEP Admin50ScientistsPrivateSlowDevelopersDesignersAuthorsCollaboration
  10. 10. Folders<Server Install> = C:Program FilesAccelrysAEP• Users: <Server Install>publicusers• Jobs: <Server Install>webjobs• Shared Public : <Server Install>public• Local Temp : <Server Install>temp• Upload : <Server Install>public• XMLDB : <Server Install>xmldb• Logs : <Server Install>logs
  11. 11. Folder: Users• Global Property: UserDir• Protocol Author:– Store data relevant to a given user– Data is not intended to be shared or used by others• Admins:– Keep track of size and what’s located in there– Plan your storage allocation and speed according to yourbusiness needs and level of Service Level– Provide guidance to Authors and Developers
  12. 12. Folder: Jobs• Global Property: JobDir• Protocol Author:– Stores data while running a job and when completed– Treat as a temporary store.– Store important results in a more permanent location (e.g. SharePoint,Corporate File Store, or ELN) using a Writer component, HTTP Connector, etc.– Any files that are in top level job folder are treated as “Job Results” to report tothe client• Admins:– This folder can grow rapidly, so you should plan on purging content based on awell communicated date range (e.g. delete items older than 2 weeks)Username Job GUID<Server Install>webjobscagramontppc4C3CB-1CF8-4B90-97E2-6F1D9DA89C33
  13. 13. Folder: Shared Public• Global Property: SharedPublicDir• Protocol Author:– When using with a Web Farm/Load Balance deployment– Store data that won’t be impacted when job folders are cleaned• Admins:– Replaces the use of “ScitegicRoot”– Oftentimes developers would use “$(ScitegicRoot)/..” to get tothe install directory
  14. 14. Folder: Local Temp• Global Properties (Both mean the same)– LocalJobTempDirectory– TempDir• Protocol Author:– Default, this is in the same folder as the job. If job is running on a cluster or grid,this I/O will travel across the network.– Can set this at the protocol level to change during a given job.• Admins:– Move the default location for all jobs away from the network location of jobs (ifapplicable)– Set location to a fast local volume– Schedule Defrag maintenance on this volume periodically. Make sure to useMaintenance Mode.
  15. 15. Folder: XMLDB• Protocol Author:– Doesn’t really care• Admins:– Backup each time you change something major in production orbefore a migration– Backup can be done using Admin Portal, DBUtil, or manually usingxcopy– In production, changes should be very infrequent. Volume locationshould favor disk read performance– Use “Windows Scheduler” or linux “cron” to create a “dbutil –backup”
  16. 16. Folder: Logs• Protocol Author:– Interested Party, but doesn’t have direct access• Admins:– Lots of information on usage, performance, connectivity, etc.– Use Pipeline Pilot to build reports– The logs/messages/*.log files do not require purging• Log rotation to limit the growth to 10MB each with one backup file• Previously growth limit was 1MB per log– Three categories of Logs (discussed more in later slides)
  17. 17. Log of Job Execution Events• <install>/logs/usage/PipelinePilot.log.• It is a structured, delimited file with one line percompleted job.• The information includes the name of the protocolexecuted, the time and duration, the client user, andwhich packages were employed.• The information is best viewed via the Completed Jobspage in the Admin Portal.
  18. 18. Log of User Authentication Events• <install>/logs/usage/access.log.• It is a structured, delimited file with one line perauthentication event.• It includes initial user login events and revalidation of theuser credentials.• The information includes the event time, the login name,the client program type, the authentication result(0=failed, 1=success, 2=reset) and the client IP address.
  19. 19. Error and Diagnostic• <install>/logs/messages• scitegicerror_NNN.log, NNN identifies a process name. Possible names are:– cgiadmin– cgifile– cgicache– cgihelp– scisvr– runprotocol– regression– dbutil– client– pkgutil– apache– aepmanager• javaserver_NNN.log, NNN identifies a java application name. Possible names are:– catalog– derby– platform– securityfilter– tomcat_shared• Files in the java subfolder - Java server error dump files, named jvm_error_<process-id>.log
  20. 20. Example of Folder separation•RAID 1 (Mirrored)•OSC:•RAID 6 (Fast, redundant)•AEP Installation, logs, XMLDBD:•RAID 0 (Fast, no redundancy)•Local TempE:•Fast Remote Storage (E.g. IBM GPFS)•Jobs, SharedDirF:•Fast Remote Storage (e.g. IBM GPFS)•Users, PublicG:
  21. 21. Tools• DbUtil.exe• pkgutil.exe• regress.exe
  22. 22. Dbutil• Command line• Great for automation• Tasks– Backup/Restore XMLDB– Backup/Restore Config– Copy tab/user folders– Purge tab/user versions
  23. 23. Packaging (pkgutil.exe)• Creating deployable units• File/Folder based• Manifest in XML(ATS6-DEV06) Using Packages for Enterprise Application Delivery
  24. 24. Regression• Test Automation• Command line• Only available on the AEP Server
  25. 25. • AEP 9 Deployment Guide is key to your planning• Plan your job folder according to usage• Educate your Authors and Users about folder usage and yourmaintenance plans• Schedule and automate your maintenance• Use Unattended Installation for repeatable deployments• Use Packages for repeatable and manageable applicationdeploymentshttps://community.accelrys.com/groups/it-devSummary

×