aXes gateway deployments
Posted: 03 Feb 2017, 11:56
What is an aXes gateway deployment?
Typical installations of aXes reside on the same IBM i server as the line-of-business (LOB) applications users operate via a browser and aXes Terminal Server. An aXes gateway deployment installs aXes on one IBM i server and provides access to applications on other IBM i servers. The gateway deployment is useful in situations where it is:
The components of a gateway deployment are:
Gateway deployments assume a minimum of two IBM i servers. One server is used as the aXes gateway and LOB applications reside on a second or more servers. A gateway deployment operates as if aXes were installed on every connected corporate server. Pages displayed by a browser will be HTML equivalents of 5250 screens from LOB servers where applications reside.
Deployment options for aXes gateway
aXes gateway offers several deployment options designed to satisfy requirements of small, medium and large companies. It supports hosting service providers managing corporate servers on behalf of several customers and ISVs providing their software as a service. You should employ appropriate security measures to protect the gateway server and enforce access control and authentication measures for people who will use aXes.
Private gateway deployments
An aXes private gateway deployment is aXes installed and operated by one company. The deployment consists of aXes on a gateway server and connected LOB servers. Users work with applications on LOB servers through aXes on the gateway server.
The deployment assumes that all users share the same instance of aXes. An alternate deployment is a dedicated instance of aXes for each LOB server; e.g. an aXes instance for each branch office.
Companies can use an aXes private gateway as way to migrate applications from an older LOB server to a new corporate server. aXes provides access to applications remaining on the older LOB server during the migration. Retire the older server when migration is complete. aXes will then provide browser access to 5250 applications operating on the new server.
Hosted gateway deployments
An aXes hosted gateway deployment is aXes operated by a hosting service provider on behalf of multiple companies each with one or more corporate servers. Company personnel, customers and suppliers use applications from their respective corporate servers by logging into aXes on a gateway server which routes them to their connected LOB servers.
Hosting service providers can deploy one or more instances of aXes. Each hosted company may have a dedicated instance of aXes or share the same instance of aXes
Use a dedicated instance of aXes for each company to ensure the separation of companies sharing a gateway server. Apart from company separation, the advantages of this deployment are the ability to customise sign on pages and enhancements to applications using aXes-eXtensions.
SaaS gateway deployments for ISVs
aXes provides independent software vendors (ISVs) with tools to offer their packaged application software to their customers using a Software-as-a-Service (SaaS) model. An ISV can install aXes on a server and instances of their application software on one or more connected corporate servers.
The ISV's customers sign on to the gateway server and are connected to the appropriate server running their instance of the application software.
ISVs install an instance of aXes for each of their customers on the gateway server. This configuration provides ISVs with the optimum separation of customer environments and facilitates customisation of graphics and colour schemes for individual customers.
Typical installations of aXes reside on the same IBM i server as the line-of-business (LOB) applications users operate via a browser and aXes Terminal Server. An aXes gateway deployment installs aXes on one IBM i server and provides access to applications on other IBM i servers. The gateway deployment is useful in situations where it is:
- Impractical to install aXes on the same server as the applications
Important to separate internet users from servers hosting LOB applications
The components of a gateway deployment are:
- Client computers are desktop, laptop or mobile devices equipped with a browser.
aXes gateway server is an IBM i server where aXes resides.
IBM i servers where LOB applications reside.
Gateway deployments assume a minimum of two IBM i servers. One server is used as the aXes gateway and LOB applications reside on a second or more servers. A gateway deployment operates as if aXes were installed on every connected corporate server. Pages displayed by a browser will be HTML equivalents of 5250 screens from LOB servers where applications reside.
Deployment options for aXes gateway
aXes gateway offers several deployment options designed to satisfy requirements of small, medium and large companies. It supports hosting service providers managing corporate servers on behalf of several customers and ISVs providing their software as a service. You should employ appropriate security measures to protect the gateway server and enforce access control and authentication measures for people who will use aXes.
Private gateway deployments
An aXes private gateway deployment is aXes installed and operated by one company. The deployment consists of aXes on a gateway server and connected LOB servers. Users work with applications on LOB servers through aXes on the gateway server.
The deployment assumes that all users share the same instance of aXes. An alternate deployment is a dedicated instance of aXes for each LOB server; e.g. an aXes instance for each branch office.
Companies can use an aXes private gateway as way to migrate applications from an older LOB server to a new corporate server. aXes provides access to applications remaining on the older LOB server during the migration. Retire the older server when migration is complete. aXes will then provide browser access to 5250 applications operating on the new server.
Hosted gateway deployments
An aXes hosted gateway deployment is aXes operated by a hosting service provider on behalf of multiple companies each with one or more corporate servers. Company personnel, customers and suppliers use applications from their respective corporate servers by logging into aXes on a gateway server which routes them to their connected LOB servers.
Hosting service providers can deploy one or more instances of aXes. Each hosted company may have a dedicated instance of aXes or share the same instance of aXes
Use a dedicated instance of aXes for each company to ensure the separation of companies sharing a gateway server. Apart from company separation, the advantages of this deployment are the ability to customise sign on pages and enhancements to applications using aXes-eXtensions.
SaaS gateway deployments for ISVs
aXes provides independent software vendors (ISVs) with tools to offer their packaged application software to their customers using a Software-as-a-Service (SaaS) model. An ISV can install aXes on a server and instances of their application software on one or more connected corporate servers.
The ISV's customers sign on to the gateway server and are connected to the appropriate server running their instance of the application software.
ISVs install an instance of aXes for each of their customers on the gateway server. This configuration provides ISVs with the optimum separation of customer environments and facilitates customisation of graphics and colour schemes for individual customers.