When designing composite applications containing Microsoft Windows applications, you must be able to access the application from the designer workstation.
To add an OpenSpan Windows Container to a composite application, do the following:
1. Drag an OpenSpan Windows Container component from the Component Library Palette, and drop it on the Composite Application Editor (CAE).
2. Right-click the OpenSpan Windows Container component in the Page Navigator, and select Edit Component Properties from the context menu.
3. In the Edit Component Properties window, select the Component Settings tab.
4. In the Title field, enter a unique name for the OpenSpan Windows Container component. Use a name relevant to the application you are using in the composite application. Note that naming the component does not set any integration properties so the component name does not need to be exactly the same as the application name.
Important: Component names should be meaningful and relevant and should be unique. It is strongly encouraged that you give each OpenSpan Windows Container a meaningful and unique name that is different than any other component in this or any other composite application.
5. Optionally, enter a description for the application.
6. Reparent App While Running causes all application top-level windows to be reparented into the container window. True is the default option. Setting this option to False causes the application windows to open independently of the composite application window.
7. Autostart App In Editor causes the target application to open when the composite application is started. False is the default option, which means that the target application is not started automatically and must be started manually by right-clicking in Composite Application Editor and selecting Start Application from the context menu. NOTE: The application also starts when the Start Interrogation command button is selected.
8. Target Environment property allows you to control whether the OpenSpan driver is used by the OpenSpan Windows Container. Use the OpenSpan driver when the target application (the application you need to monitor or control) is not directly launched by the component, such as when the target application is launched by the application started by the component or by a desktop shortcut selected by the user.
There are two Target Environment settings:
- Driver. This default option loads the OpenSpan driver when the project starts. Use the OpenSpan driver when the application started by an OpenSpan Windows Container component, as defined by the component’s Path property, is not the application that you need to control or is not the only application used. This setting makes all the Start methods available: Start, Start and Wait, and MonitorAll.
- NoDriver. The OpenSpan driver is not loaded when the project starts. Use this setting when the process specified by the Path property for all project adapters are the only processes used in the project. Note that the NoDriver option limits the Windows application Start Method to Start.
9. Open the Interrogation tab.
10. Set the Path property to the location of the target application by entering the full path to the executable file. Use the Folder property to set the runtime location of the application in cases where the path to the application is different on the runtime workstations than the path on the OpenSpan Studio designer workstation.
11. Set the Target Path if you need to hook into a single process that is launched from the process that was started from the Path location.
12. Set the HookChildProcesses property to True if the target application launches additional applications that you want to include in the composite application.
13. Use the Interrogation function (Start Interrogation button) to select the targets from applications that you want to include in your composite application.
14. Modify the match rules as necessary to ensure that all targets are uniquely matched.
15. Select OK to save your changes and dismiss the Edit Component Properties window.
for OWC users with multiple Internet Explorer containers in a composite application. It's possible for multiple IE instances to appear under the same Java Swing tab on the UI. This is due to Internet Explorer launching the requested Web page into an existing session under certain circumstances.
The solution is to add
the following to the Arguments Property
when launching iexplore with OWC:
- Internet Explorer Versions 6 and 7: -new
- Internet Explorer Version 8: -restart -nomerge