isCOBOL Application Server
isCOBOL Evolve delivers a choice of deployment architectures without complex implementation requirements. isCOBOL programs can run locally or be distributed from a server with isCOBOL Application Server, simplifying distribution steps and improving time-to-market for key applications. With isCOBOL Application Server, applications are easily distributed to take full advantage of today’s multi-threaded processing capabilities on a variety of platforms including UNIX, Linux and Windows.
- Delivers 100% portability by supporting any platform that runs the Java Virtual Machine
- Eliminates the need to use a different debugger for every deployment platform; written 100% in Java
- Eliminates the need to maintain separate user interface code for different deployment platforms
- Offers bi-directional processing -- clients can start programs on the server and vice-versa
- Delivers advanced thin client and distributed processing functionality at a good value because these features are included in the isCOBOL Runtime Environment
- Offers an optional load balancer for enhanced horizontal scalability or workload separation
All clients can be created equal
Since isCOBOL Evolve is Java based, developers leverage the same GUI, regardless if the client is Windows, UNIX, Mac, handheld, etc. The user interface and all of its program functionality developed in isCOBOL will work the same whether the application is deployed locally or distributed across a network -- simplifying development and maintenance.
isCOBOL Application Server provides a thin client that can be automatically downloaded and run as a standalone Java program. isCOBOL Application Server runs the application on the server machine with just the user interface running on the client. When running with a thin client, the user interface is identical with what is seen when running locally. In other words, the thin client user interface supports every window and graphical control type, style and property, as well as all text-based elements. There are no differences in the user interface when running locally verses thin client and developers do not need to "program to" or "design for" isCOBOL Application Server software's thin client capabilities. Once a user interface is working as desired in local mode it can then be deployed in thin client mode with complete confidence that there will be no differences across platforms.
True multi-threaded processing
isCOBOL Application Server is multi-threaded and utilizes true processing threads, not emulated threads. With isCOBOL Application Server, each program runs in a separate thread, not a separate process on the server; COBOL programs can start multiple threads and multi-task. This means that it consumes far less resources on the server and has a much faster startup response time for the end-user, conserving system memory and saving valuable CPU cycles. In addition, isCOBOL technology is bidirectional, so server applications can call programs on a client and client programs can call programs on the server.
Portability without the additional price
isCOBOL Application Server provides high value by conserving valuable system and network resources and by including thin client and distributed processing capabilities into the base runtime environment.
isCOBOL Application Server makes the deployment process smoother because an application is loaded only on the server. Nothing is needed on the client side, except a Java Runtime Environment (JRE) and the isCOBOL thin client Java library. The isCOBOL Application Server accepts each connection, creates a separate thread for the user session, and runs the COBOL application projecting just the user interface onto the client display.
For organizations with numerous thin client end-users or specialized computing requirements, the isCOBOL Load Balancer is available an add-on product to isCOBOL Application Server. The isCOBOL Load Balancer distributes workloads among clusters of server processes running on the same or different machines for enhanced horizontal scalability or workload separation.
Once the isCOBOL Load Balancer is started, it waits for connections from isCOBOL clients and when a connection request is performed, it evaluates the best server for satisfying the request, and then supplies the address of that server to the isCOBOL client. From that moment, the isCOBOL client communicates with the isCOBOL Application Server directly and the connection between the isCOBOL client and the isCOBOL Load Balancer is closed, therefore shutting down the isCOBOL Load Balancer does not have an impact on current connections. Options and parameters for the isCOBOL Load Balancer can be set with the load balancer panel in the isCOBOL IDE.
Learn moreView the isCOBOL Evolve Datasheet
Learn more about the newest isCOBOL Evolve Release
Contact Veryant to arrange a complimentary code analysis or learn more about isCOBOL