1 / 18

Set up of W2K consoles

Set up of W2K consoles. The Operational Software Prospective. Set up of W2K consoles. Administration of user opera Software deployment Requirements Java Applications IT supported applications Run-time environment Unix software Launch operational applications Resources Work.

martina-mclean
Download Presentation

Set up of W2K consoles

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Set up of W2K consoles The Operational Software Prospective Eugenia Hatziangeli (SL/CO/AP)

  2. Set up of W2K consoles • Administration of user opera • Software deployment • Requirements • Java Applications • IT supported applications • Run-time environment • Unix software • Launch operational applications • Resources • Work Eugenia Hatziangeli (SL/CO/AP)

  3. Administration of user opera • Centrally based Mandatory roaming profile: • Not possible to save local profile • Only user opera (+ experts) allowed to log on operational consoles • No software installation privileges Eugenia Hatziangeli (SL/CO/AP)

  4. Administration of user opera • No Internet access • Define a group policy to: • assign[obligatory]/publish[optional]/deny all necessary application • deploy certain type of applications • desktop settings • security settings Eugenia Hatziangeli (SL/CO/AP)

  5. Software Deployment It is the process of systematically moving software applications or components from a central source to the target community of end-users. It is the critical last step in the process of creating software. Eugenia Hatziangeli (SL/CO/AP)

  6. Software Deployment Requirements: • Mainly Java applications (few PVSS applications by ST) • Access to Unix file system (data, configuration files) • High startup performance • Applications run locally, but upgrade automatically if new version • No application will relay on locally saved information • Security – only user opera (+experts) can launch applications • Ease of use for developers and users Eugenia Hatziangeli (SL/CO/AP)

  7. Operational distribution area Razor repository Release tool PCROPS Development software Extract release from Razor Compile on OP platforms Install new version Distribute public deliverables Operational software SAMBA (HPDEPOT) Jar, JNLP files Web Server W2K Operational console Software Deployment • Java Applications – The proposed solution Eugenia Hatziangeli (SL/CO/AP)

  8. Software Deployment Unix file access: • Provided by Samba server on HPDEPOT • Only user opera (+experts) can access operational distribution areas) • Transparent file access (TBI) Eugenia Hatziangeli (SL/CO/AP)

  9. JaWS Software Deployment -JaWS • User clicks on a download link, the link instructs the browser to invoke JaWS technology. • JaWS technology queries the Web to determine if all the resources needed for the application are already downloaded. If they are, and the most recent version of the application is present, the application will be launched immediately (step 3). • If the resources are not present or an update is available, JaWS downloads the needed resources. Thus, the initial download and subsequent updates of an application happens transparently. Eugenia Hatziangeli (SL/CO/AP)

  10. Software Deployment - JaWS Some important issues • It is provided by SUN free of charge • JaWS allows to launch Java-technology-based applications directly from the Web =>Need to set up a web server (support – maintenance) • Launches only Java-technology-based applications • Java application is distributed as a set of JAR files • Special Java Network Launch Protocol (JNLP) file has to be created (one for each application) Eugenia Hatziangeli (SL/CO/AP)

  11. Software Deployment -IT applications IT supported applications, e.g. Exceed, Excel, etc. • Use IT supported deployment solutions • Use notion of machine groups and user groups with group policies • All necessary applications will be assigned to a combination of the above two groups • They are installed at boot (m/c) or at login time (user) Eugenia Hatziangeli (SL/CO/AP)

  12. Software Deployment – Run Time Run time environment, e.g. • JVM • IT does not provide it or support it • The appropriate JVM will be locally installed by SL/CO/AP • JIntegra • It will be locally installed by SL/CO/AP Eugenia Hatziangeli (SL/CO/AP)

  13. Unix Software • Access to all Operational Unix software via HummingBird Exceed v7.0 • Exceed configuration files stored centrally and assigned to user opera group policy Eugenia Hatziangeli (SL/CO/AP)

  14. Launch of the operational applications • At present all available applications are launched via Start menu • Java Web Start can launch applications from: • Web browser by clicking on a link • JaWS built-in Application Manager • Desktop icons or the Start Menu The console manager will be a separate activity Eugenia Hatziangeli (SL/CO/AP)

  15. Security CERN domain AccOperations domain Zone Computers Users c1w055 c1w064c1sba1 opera experts pickets PCR Computers pcopcr01 pcopcr02 pcopcr03 Only users in our domain can log in to domain PCs • No opera (+ experts) login from PCs outside our domain No TCP/IP external connection • Machines outside CERN cannot access our PCs • No access to Internet Private Firewall • Accept packets only from SL (ST, PS) subnet • Accept packets from outside when the communication started by a m/c inside the authorized subnets. Install ssh for Exceed • Passwords, session, X11 are encrypted Access from home • Secure access to the control system =>TBI Eugenia Hatziangeli (SL/CO/AP)

  16. Resources The Team SL/CO • Eugenia Hatziangeli • Sebastian Lopienski SL/OP • Markus Albert • Guy Crockford Collaborators (as users) • SL/BI (S. Jackson) • SL/PO (S. Page) • ST/MA (U. Epting) Collaborators (support) • SL/CO/FE • SL/CO/WS Eugenia Hatziangeli (SL/CO/AP)

  17. Done Collect requirements for deployment User opera set up phase I (limited privileges) Set up Exceed for user opera Evaluate several deployment solutions Access to pcrops/biswop via HPDEPOT Deployment solution is decided W2K admin training The work To be provided • Create/populate private W2K domain for acc. operations • User opera set up phase II - group policies (appl. assingments, desktop sets, etc.) • Mandatory profile, startup menus, config. files (Exceed) • Set up the Web Server for sw deployment • Deploy JaWS in operational consoles By when • Finish setting up by end Dec 2001 • Available to the users by end February 2002 – End of work Eugenia Hatziangeli (SL/CO/AP)

  18. What we expect • If any concerned user was left out (accidentally), now is the time to speak up • Equipment groups that they would like us to set up an expert user login, let us know Eugenia Hatziangeli (SL/CO/AP)

More Related