Posted: 18 Aug 2016 14:22 EDT Last activity: 4 Oct 2018 13:54 EDT
Using Openspan and Pega to automate mainframe system related activities
There is a process which requires user to access mainframe and perform series of steps in various screens of that mainframe. There will need to be decisions taken and accordingly need to access different screens on the mainframe system, as well as access multiple instances of the mainframe for validation and cross verification purposes.
1. Is this possible in Openspan?
2. Assuming Pega is also available at our disposal, how can we have a combination of Pega and Openspan to achieve the result?
***Updated by Moderator: Marissa to add Robotics Group Tag***
***Updated by Moderator: Marissa to update categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Yes, OpenSpan (Pega Robotics) can integrate with mainframes. We do it through the emulator which must be a version that supports the HLLAPI API interface (most paid emulators do). There are a number of ways to integrate a robot with Pega, both with older versions of Pega and the latest releases of Pega. First we an integrate on the desktop alongside the pega application (Robotic Desktop Automation or RDA). Second, we can integrate with robots running server-side connecting to a Pega application via Web Services. Obviously, we make the integration a bit easier if you are on the lastest release of Pega but we can still accomplish with older versions of Pega.
The users are lodging claims in the mainframe. On completion of the lodgement, we need to trigger from mainframe to extract few details and to create a shell claim on a new browser based claims application.
As far as I know there is no video. Look in the help under Application Integration\Text (Host) Applications. There is a ton of information there to get started. Essentially, you will use two adapters; a windows adapter to start your session and get it connected, and a text adapter of some kind to interrogate the emulator screens. The former will start the latter once the session is up as the text session will fail if that short session isn't running already.
You'll need to make sure your emulator supports HLLAPI and has it enabled. You'll need to know the Short Session Name of the session (or you may have to set it if HLLAPI is not being used).