The GC product enables the user to define web services. In the core of these services are XSLT files which transform the user provided data from JMS message format to SOAP, as well as from SOAP to JMS. In case of fault, a fault XSLT is provided. The XSLT files are provided by the user. These web services can be collected in order to define a Gateway Console configuration that can be later uploaded to the corresponding BW engine. The configuration is an XML file which contains the definitions of the assigned services to that configuration. The XML GC configurations are uploaded from the database to the TIBCO BW engine using the HTTP protocol.

The GC project offers administrator and user interfaces with corresponding privileges. The administrators define users and groups, services and assign privileges to the users. They can manage the loading of the XSLT files, as well as define configurations and define engine properties. GC can synchronize its users and groups with those on an LDAP server and also supports robust logging mechanism.

 The other part of the product designed using the TIBCO/BusinessWorks and is responsible for accepting HTTP requests for configuration and xslt files upload, storing the received configuration and xslt files in the memory cache, backup of the previous configuration and writing the received configuration and xslt files on the disk.

The GC product follows the Struts framework design patterns, which includes custom Java classes, JSP, JavaScript, JSTL, Struts tag libraries, Action and ActionForm classes, Data Transfer Objects etc. The logging is realized using log4j. It uses Oracle 8i and can run on WebLogic, JBoss and IBM Web Sphere servers. The interaction with the user can be done using the thin client that can be either Internet Explorer or Netscape Navigator.