Loading in 2 Seconds...
Loading in 2 Seconds...
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. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
IBM RDz (7.6) with CA Endevor Eclipse Plug-In(The Latest Update) Helping customers achieve the consistent Application Lifecycle Management ‘workflow’ with measurable returns Keith Allen CA EMEA Team Lead ALM Activities
Objective • Introduce you to the Updated (Sept 09)Endevor Plug-in for working within the IBM RDz (7.5 and above) • Review the CA CMEW r12 integration through the Eclipse Plug in • Review the IBM RDz Endevor Eclipse view • Understand the benefits and target audience • See the plug-in in action, through a live demo • Discuss installation and support issues
Agenda • Introduction • Architecture • Demo • Infrastructure • Endevor RDz Plug in with IBM’s RDz • Debugging aids and tips • Queues and contacts • Q&A
Introduction • The plug-in provides a “duel” developer interface to an Endevor set up • Off mainframe (windows based) direct element editing • Off mainframe (Web Based) Endevor access and control. • MF security is still the driver… • BUT NO TSO SEGMENT NEEDED (save on TSO Resources) • The Eclipse Base provides the base ISPF Quick Edit facilities with additional non MF features (local History etc) • Certified for Windows Eclipse 3.5 and below and IBM’s RDz (7.5 and above)
Introduction • What do developers do? • Browse elements • View processor output • Modify elements and rebuild executables • Require remote debugging facilities
Architecture Diagram Eclipse 3.x CMEW Server Z/OS Repository AddOpen BrowseSaveView Listing CMEW Web/JSP Server Endevor EndevorService CMEW(ew) CMEW STCs JES TSO Or… CCI CCI ENF USS RDz Repository AddOpen BrowseSaveView Listing CMEW z/OS Support MDB Enterprise DB
Prerequisites for the Plug-in • 3rd Party Components (optional) • Eclipse 3.5 SDK • Java Runtime Environment (JRE) from Sun. • CA Components • EndevorService.war (aka Plug-in Companion) • CM Enterprise Workbench r12 • Endevor r12 SP3 • IBM Components • RDz 7.5 or above installation • (required RDz Options – CIC, IMS…)
IT’S Demo Time! • Workflow detailed in online help • Create Repository • Create Project(s) • Select elements of interest • Wash, Rinse, Repeat • Delete Project • Delete Repository
And the results Repository View Search Map View Endevor Log View Element View
Add an element to a project The Element View
Default Context Actions • Project View – Open (for update) • Search Map and Element Views - Browse
Adding a new element • Add Navigator View to perspective (Windows->add View->Navigator • Select file to add or File->new->File • Edit new file • On Navigator view select new file right click->Team->add to Endevor
Access to CMEW • Endevor->AllFusion Enterprise CM
Entry Stage Cleanup • Delete on the element context menu deletes the element from the entry stage.
CA Software Change Manager Interface with Eclipse Schematic of Eclipse RDz à CA CMEW à CA Endevor
Preview: RDz with Endevor Plug-In Adding EGL Source via CMEW Package EGL Source and Store In Endevor Within the RDz Project Explorer it is a simple Copy from the EGL Package and Paste over the Endevor Project to prepare to add EGL into CA Endevor on z/OS. Then Update the Endevor Project with the appropriate Change Control Identifier (CCID to relate all objects) from your existing Change number for the new application (or enhancement). Then use the Team (drop-down) to add to Endevor). The only prompt is for the Processor Group – EGL. Then the egl (with the long or short names) are propagated to CA Endevor. The Endevor Log will identify the results. Ensure Relationship Between EGL Source and Generated Cobol As part of the RDz Generate – COBOL source (and any ancillary files) are passed to a JCL processes executed on the z/OS. This process has an Endevor step that adds these objects into Endevor and runs a Process (Pre-compile, Compile and optional Bind) using the CCID specified as a comment. Now the EGL and COBOL source is related with the CCID. All elements (current and previous) can be returned to RDz via this unique CCID. (Note: DB2 DDL can also be implemented as objects in CA Endevor from RDz).
Q&A • Questions? • Comments?