Automatically identifying screens and map steps using trace files (GCT)
SSL connection between .NET base object/framework and ApplinX server
New embedded database to be used as the ApplinX application repository
The Screen Process Extractor extracts process-relevant data from 3270/5250 screens and provides it to ARIS PPM. The Screen Process Extractor is based on ApplinX technology, however, the data can be extracted from virtually any terminal emulation on the market.
In order to implement the Screen Process Extractor, ApplinX designed, Business Activity entities are required. These are created in ApplinX Designer and are used in the Business Process Analysis when analyzing trace files. The Business Activity entity enables defining rules and conditions that are later searched for when analyzing trace files. Once these rules and conditions are met, the relevant information regarding the activity is detailed in an XML file. The XML file is then loaded into ARIS PPM where they can play a part in analyzing a broader Business Process.
Note:
A BPD license is required for this feature.
Refer to Screen Process Extractor for further details.
This feature enables redirecting emulation network traffic to pass through the port configured in the Application Properties (only relevant for AS/400 and Mainframe hosts). This feature is particularly required for two new key features:
Screen Process Extractor: Used to collect user's trace files using their existing communication with the hosts.
Automatically identifying screens and map steps using trace files.
ApplinX trace files have been enhanced and now include the following capabilities:
Trace files can now be compressed to save space on the disc. This is particularly suitable when tracing a large number of files on a regular basis.
Trace files can now be encrypted.
Trace files can now be saved in separate directories per Day, Month and year. This is particularly useful when tracing a large number of files on a regular basis.
Refer to Recording Trace Files for further details.
ApplinX has introduced a new wizard which enables using a trace file (GCT) to:
webMethods Integration Server supports the integration of diverse services, such as mapping data between formats and communication between systems. ApplinX procedures can be registered as services in webMethods Integration Server.
ApplinX procedures enable providing credentials to execute Integration Server services.
For further details, refer to Registering a Web Service to webMethods Integration Server.
Two changes have been made in the CentraSite integration:
It is no longer necessary to define a username and password for connection to CentraSite as the username and password defined in the CentraSite plugin preferences are used.
ApplinX now uses an aar file to register ApplinX procedure groups as services in CentraSite. The process has changed and now you need to first export the Procedure Group, and then generate an aar file (right click on a procedure group and select to generate the aar file and then in the Java perspective right click on the aar file, deploy it to WS-Stack and then right click again and register it to CentraSite).
When migrating previous ApplinX versions to the current version, Path Wrappers work in runtime, but cannot be edited. There is now a conversion process which converts these Path Wrappers to Path Procedures. Details regarding this process are included in the Post Migration Tasks.
Note: When converting a Path Wrapper, the path which is invoked by the path wrapper is also converted. When converting a Path which is invoked by a Path Wrapper, the Path Wrapper is also converted.
An image of the Procedure tree can be saved as a PNG file for later reference, by right-clicking on the Procedure root node, and selecting
When using the Replay Trace File Navigator toolbar in the Session View, it is now possible to select the name of the screen you would like to navigate to. It is also possible to search for screens associated with a specific screen group, by selecting the screen group. Refer to Using the replay navigator within the Replay Mode Navigation section for further details.
In this version, it is possible to create .Net Web applications and Procedure Clients in Visual Studio 2010.
Migration from previous Visual Studio versions is now available.
ApplinX .Net Base Object now supports SSL connection to ApplinX Server
ApplinX now offers using an internal built-in ApplinX database to use as the repository. This improves performance, simplifies the repository configuration process and performs automatic synchronization during the migration process. The embedded database is listed in the list of repositories that can be selected when determining the database ApplinX is to work with. The embedded database is now used by default when defining a new ApplinX Application.
Support has been added for the following code pages:
cp274 (Old Belgium)
cp1130 (Vietnamese EBCDIC)
Session Data is an entity, based on data structure, used to save session context information. Each application has a single Session Data entity, located in the Repository folder. The Session Data entity enables defining variables and their types in the session context during design time. In Runtime, a Session Data object is created for each user session, and it is possible to set and then use the variables' values in the current session. The session data can be useful to save user information during the session.
