The Component Enabler client workstation is the workstation through which users access Component Enabler applications. You need the following software on your client workstation:
Notes:
These applications do not require the JDK or the C# compiler on the client workstation.
For Java applications that use Component Enabler, you need a Java Virtual Machine, such as the Oracle Java Runtime Environment, Version 1.6 or later .
For applications that use the Component Enabler for .NET interface, you need:
The Microsoft .NET Framework 4.7.2 or later.
You do not need a Web browser.
When running the Presentation Client as a standalone application, or the JSP Client, you need:
An operating system with TCP/IP services installed, for example, Windows 10 Enterprise (x64) Professional, Enterprise (x64) October 2018 Update or Mac OS X.
A Java 1.6 or higher Virtual Machine (JVM), such as the one supplied by Oracle.
When running the Presentation Client from a Web browser, you need:
An operating system with TCP/IP services installed; for example, Windows 10 Enterprise (x64), Professional (x64) October 2018 Update or Mac OS X.
One of the following qualified browsers:
Microsoft Internet Explorer 11.0 or later
FireFox or later
Safari (for MAC OS X)
Java version 1.6 or later, compatible plug-in.
Note: These applications do not require the JDK on the client workstation.
For applications that use scripted pages on a Web server, you need an operating system with TCP/IP services installed; for example, Windows 10 Enterprise (x64) Professional, Enterprise (x64) October 2018 or UNIX®.
Remote Access Server
To communicate with a Component Enabler client, you need the following software on the server for the host system:
Agile Business Suite Runtime
TCP/IP
Remote Access Server software
Note: After the Remote Access server software is installed, you need to create Component Enabler Views before using the Remote Access servers to access the system. Refer to the Agile Business Suite Runtime Administration Guide for your host platform for more information.
The Client Framework client workstation might be an end-user workstation or a server machine. A new connection mechanism, Access Layer API, is available in the Client Framework for connecting a client to the runtime system. The Access Layer API allows the client application to interact with the deployed AB Suite system and is exposed through Direct and Remote connection.
For direct connections, the client workstation requires the following software:
.NET Framework 4.7.2 or later
Access Layer API assemblies
Data Models assembly for an application
Application specific components. For example,
Data View Models and Views assemblies for a WPF Client application
Any dependent software required by the client technology that was used to develop the client application such as custom WPF Toolkit
Client Framework WCF Gateway Services
To remotely access the runtime system for Client Framework applications, the following AB Suite WCF gateway services are installed:
AB Suite 7.0 Client Framework (WCF) FileStore Gateway – Allows Client Framework clients to retrieve or store files, such as images.
AB Suite 7.0 Client Framework (WCF) Gateway – Allows Client Framework to access an AB Suite System over TCP/IP.
These services are installed when you install the AB Suite Runtime for Windows, and client applications can use them to interact with the deployed AB Suite runtime system.
For Developers, the Client Framework WCF Gateway Host application is also installed with the AB Suite Developer for Windows software. This is a WCF Service hosting application that can be used to test the WCF Gateway services on a machine where the AB Suite Runtime software is not installed. Refer to the Agile Business Suite Developer User Guide for more information on the WCF Gateway Host.
WCF follows a client-server model to establish communication between applications. The AB Suite WCF gateway can be
Self-hosted in any managed .NET application
Hosted as a Windows service
Hosted in different versions of Internet Information Services (IIS)
Refer to the MSDN documentation for more information on hosting and consuming WCF services.
The remote Access Layer API uses .Net Portable Library assemblies. It can be used wherever portable libraries are required. For example, Windows 8 Store Apps, Silverlight , and Windows Phone 8 clients.
To enable Client Framework applications to connect to the runtime system remotely, the client workstation requires the following:
.Net Framework Portable subset
Access Layer API Remote assemblies
.Net Portable DataModels for the application
Application specific components. For example,
DataViewModels and Views assemblies for a SilverLight client application.
Any dependent software required by the client technology that was used to develop the client application, such as custom Silverlight Toolkit.
The WCF Gateway server requires the following:
.Net Framework 4.7.2 or later
Access Layer API assemblies
.Net DataModels for an application
To configure the WCF Gateway, you must modify its associated configuration file, Unisys.ABSuite.AccessLayer.GatewayServiceLibrary.dll.config, which is installed in the Bin folder of the AB Suite installation directory.
Refer to the MSDN documentation for more information on configuring WCF Services and the options you can specify in the configuration file.
Client Framework Custom Service Libraries
If you have developed a custom WCF Service by using the Client Framework WCF Service technology option, you can install the associated WCF Hosting application as a Windows Service to host your Service Library.
You can install the associated WCF Hosting application as a Windows Service by running the following command from the command prompt:
InstallUtil <SegmentName>.<FolderName>Gateway.exe
To run the WCF Service with a specified user name and password, you must run the following command from the command prompt:
InstallUtil /user=<username> /password=<myPassword> <SegmentName>.<FolderName>Gateway.exe
Notes:
You can run the WCF Service by using the Application User account. Alternatively, you can use a credential that has similar rights as the Application User.
If you do not specify a user name and password, the WCF service runs as a local service.
Refer to the Agile Business Suite Developer User Guide for more information on creating a custom service library.
To configure the custom service library for your WCF Hosting application, you must modify the necessary tags in the app.config file. The app.config file is created on the generation of the service library project.
When you host this gateway you can find the app.config file in the Solution Explorer window under WcfServiceLibrary project.
Refer to the MSDN documentation for more information on configuring the WCF gateway.