🙟 Enterprise Studio is a graphic design IDE for components that communicate with applications installed on a Mainframe (IBM z/OS, AS400, Bull GCOS, etc.)
🙟 Enterprise Studio allows you to produce components such as screens, Access Objects in Java, data components representing Cobol copy book or flow services to base an SOA on a screen application
🙟 These components are ready to be used in the environment best suited to e-business developments (portals, application servers such as Weblogic, Websphere, and other J2EE environments) under Mainframe Integrator
🙟 An Access Object is a component that automates part of the navigation in a Mainframe application accessible via screens.
🙟 The terminal editor of SCORT Enterprise Studio Screen Editor allows you to build such components.
🙟 When designing Access Objects it is necessary to determine how the connection will be used:
Mode Stateful : the connection is left in a variable state and the components run in a specific order (dedicated connections are generally used). The caller must manage this state.
Mode Stateless : the components make connections each time by repositioning them in the same state and can be executed in any order (shared connections can be implemented).
🙟 The project consists of a file suffixed by .esprj and an associated directory of the same name.
🙟The elements of the project are physically gathered in this directory.
🙟 The workspace is divided into panels that can be reduced or restored by clicking on the arrow :
🙟 The control panel contains : ○shortcuts to useful commands (open, save, search, generate, execute). ○the tabs for accessing the explorer or projects.
🙟 A project centralizes and organizes the resources of an application.
🙟 These resources are Enterprise Studio specific files or other more common files.
🙟 Open projects are accessible through the control panel.
⇨The contents of the Workspace are displayed in the Project Manager window.
🙟 TheWorkspace can be divided into sub-directories that allow you to organize project resources.
About Terminal Editor
🙟 The terminal component is a resource of Enterprise Studio Screen Editor.
🙟 It allows you to develop components that access a Mainframe application via screens by:
Instrumentation of screens,
Design of Access Objects which automate part of the navigation.
🙟 Functions of the terminal editor:
Connect to the application,
Take screenshots and transactions,
Edit screens and transactions (Access Objects).
🙟 A Terminal Editor has 3 views :
🙟Items captured with ES (screens and transactions) are stored in the Repository. There are three views to access these elements (mixed, screen, AO) :
🙟 Repository screens :
Captured screens are organized in lists
The placement of screens in these lists is free
A filter, input and output data are defined for each screen
🙟Repository transactions :
The term transaction is here synonymous with Access Object
Transactions are classified in lists
A transaction describes a sequence of screens allowing navigation in the Mainframe application
🙟 The emulator is used to navigate the application.
🙟 It also allows direct capture of screens or transactions.
🙟 This view allows you to define the configuration of the emulator, generation and documentation parameters.
Depends on the type of terminal used to connect to the application: screen size, host, port, read, TP, language, …