Inprise Application Server 4 – Features & Benefits


Complete J2EE Implementation
IAS4
Complete EJB 1.1 implementation
V
Stateless Session Beans
V
Stateful Session Beans
V
Entity beans with Bean Managed Persistence (BMP)
V
Entity beans with Container Managed Persistence (CMP)
V
Support for Java Servlets
V
Support for Java Server Pages (JSP)
V
Java Naming and Directory Interface (JNDI)
V
Java Database Connectivity (JDBC)
V
CORBA compliance with both RMI-over-IIOP and Java-to-IDL mapping
V
Demonstrable interoperability with established CORBA products
V
Java Transaction Service (JTS) and Java Transaction API (JTA), and integrated support for 2-phase-commit to allow each transaction to span multiple EJBs, multiple containers, and multiple databases
V
EJB 1.1 XML Deployment Descriptors, environment references in JNDI
V
Java Messaging Service (JMS)
V
Full Support for Java2 
V
EJB Container  
Implemented completely in Java, for portability across platforms
V
Interoperable with EJB containers from other vendors, that conform to the EJB 1.1 Interoperability guidelines
V
Instrumented for management
V
Unparalled support for various Client technologies leveraging on the duality of implementations of EJBs, Naming Service, Transaction Service, etc which expose both Pure Java and CORBA IDL interfaces
V
Demonstrable ability to deploy any compliant set of enterprise beans into the container without modification 
V
Container can run in standalone mode which gives ease of use for developers.
V
Container has small footprint compared to the competition
V
EJB Session Beans  
Optimized pooling of Stateless Session Beans, to minimize the number of stateless session beans needed in the container
V
Optimized pooling of Stateful Session Beans, to minimize memory usage by the state of stateful beans
V
Number of stateful session beans supported in container is orders of magnitude more than the competition, for very high scalability
V
Passivation of stateful session beans into a local file-based database or a remote database using a Type 4 JDBC driver, for better resource management and increased fault-tolerance and failover capability
V
Configurable passivation intervals
V
Configurable idle-timeouts
V
Configurable sizes for session bean pools
V
Client using Stateless Session Beans can transparently failover to beans in another container 
V
Clients using Stateful Session Beans can also transparently failover to beans in another container, using integrated session state management repository, for fault-tolerance that goes beyond the EJB specifications
V
Session Synchronization Interfaces, to allow stateful session beans to synchronize database data that they may have cached during a transaction
V
Support for correctly passivating session beans which contain references to other session beans, entity beans, and Home objects
V
EJB Entity Beans  
Optimized caching of entity bean data with support for all EJB 1.1 specified options for entity bean caching, to increase performance
V
Support for Bean Managed Persistence (BMP) using the application programmer’s choice of persistence mechanisms, with no restrictions
V
Support for Container Managed Persistence (CMP), to transparently map entity beans to database tables without coding
V
Integrated transparent Object-to-Relational (OR) Mapping, with mapping information optionally captured in XML for sophisticated mappings
V
CMP implemented using standard JDBC, to allow any data source with a JDBC driver to be used by the container
V
CMP engine explicitly validated and tuned with Oracle, Informix, Sybase, DB2, SQLServer, InterBase, and JDataStore
V
CMP Engine has knowledge of different SQL dialects and unique data types, for Oracle, Informix Sybase, DB2, SQLServer, InterBase, and JDataStore
V
SQL Where clauses for finder methods can be specified in XML deployment descriptor with no coding required by application developer
V
Tuned Writes in CMP, which updates databases with only the changed fields of beans and often completely eliminates trips to the database if a transaction does not change a bean’s state
V
Ability for a single entity bean in a single container to be invoked simultaneously by multiple clients and safely participate in multiple concurrent transactions, which provides huge performance boosts in applications where certain entity beans are used frequently
V
CMP Support for Composite EJBs, configurable in the XML deployment descriptor, which allows CMP EJBs to “contain” other beans (e.g., BookBean contains AuthorBean)
V
OR Mapping & CMP Support for mapping one entity bean across multiple tables
V
OR Mapping & CMP Support for mapping one entity bean across multiple databases
V
OR Mapping & CMP Support for loading entity beans from one set of tables and storing them to a different set of tables, possibly in multiple databases
V
OR Mapping & CMP Support for loading entity beans from a view and storing them to tables, possibly in multiple databases
V
Ability to use a mixture of BMP and CMP on the same entity beans
V
IAS4 CMP makes extensive use of Java Reflection with intelligent caching, to eliminate the need for code generation for persistence
V
Additional ease-of-use finder methods in addition to standard ones required by EJB 1.1, for increased usability
V
Ability for server programmers to specify the SQL statements that should be executed to find EJBs in databases
V
Intelligent handling of NULL values in databases
V
Ability to map database columns to EJB instance variables of primitive types or object types
V
EJB References & Links, allow developer to specify constraints and relationships between EJBs, which the container will automatically establish
V
Entity Beans can be configured to have “Exclusive” access to the tables it is mapped to, to allow the container to cache the bean across transactions
V
Entity Beans can be configured to have “Shared” access to the tables it is mapped to, to disable caching of the bean across transactions, but still avoid extraneous activation & passivation
V
ejbFindByPrimaryKey can be configured to simply verify that the primary key exists, or eagerly load the object, or defer key verification until the key is needed, to tune performance for each application
V
Highly optimized configurable caching schemes for finder methods that boost performance by 300% or more, when compared to the competition
V
Entity-bean Ready-Pool, for beans associated with primary keys, with configurable size
V
Entity-bean Cache-Pool, for beans containing data, with configurable size
V
Configurable ability for CMP to reuse prepared statements in the container across transactions, to minimize the number of JDBC Statement objects created and conserve resources
V
CMP Service Provider Interface (SPI) exposed, to allow substitution of other CMP implementations (e.g., object databases, proprietary in-house persistence mechanisms)
V
Integration with leading OR Mapping tools, such as ObjectPeople TOPLink, for enhanced CMP
V
Support for reading and writing arbitrarily complex Java objects to database fields without requiring coding by the application programmer
V
Configurable type-transformations, which allow the application programmer to make arbitrary mappings Java/EJB data types to database data types, which allows mapping to JDBC2 extended types such as structs or arrays
V
Optional automatic creation of tables (and relevant indexes), for all SQL dialects mentioned above
V
Ability to map loading & storing of entity beans to database stored procedure(s), for unlimited sophistication in OR mapping
V
Overridable/customizable primary-key generation, for increased flexibility and integration with new and existing database application
V
Ability to easily incorporate existing SQL or stored procedures into the lifecycle of entity beans, for legacy integration and preserving existing, tested, business rules
V
Support for locating JDBC data sources using JNDI
V
Intelligent Relationship Management  
Container support for 1-to-1 relationships
V
Container support for 1-to-many relationships
V
Container support for many-to-many relationships
V
Support for lazy loading of related objects as relationships are traversed
V
Distributed Business Logic  
Each container in a cluster can host a different set of bean classes
V
Each container in a cluster can host a different set of bean instances
V
Support for packaging multiple beans in a single Jar file
V
Multiple Jar files can be deployed to the same container
V
Support for EJBs of the same types, but in different containers, to automatically become failover replicas of each other
V
Clients using Session Beans (both Stateful and Stateless) and Entity Beans (both BMP and CMP) can transparently failover to beans in another container because Inprise JTS’s integrated 2-phase-commit ensures transaction semantics even if the new beans are in a different container
V
Application can be reconfigured, repartitioned, and redeployed by changing only EJB environment entries, without requiring coding changes
V
VisiBroker and CORBA integration  
Ability to instantiate CORBA objects and EJB in the same container
V
Support for Portable Object Adapter (POA), which provides for sophisticated management of server object lifetimes, and allows server source code portability across ORB products
V
Objects By Value (OBV), for passing of arbitrary complex objects and graphs of objects by value across processes, machines, and languages
V
Valuetypes, the OMG-specified mechanism for encoding and passing objects by value which allows interoperability of OBV across ORB products
V
RMI-over-IIOP, which is mandated by the EJB 1.1 specification, for interoperability between containers from different vendors
V
Java-to-IDL Reverse Mapping, which allows CORBA clients (potentially non-Java clients) to invoke EJBs
V
IDL-to-Java Mapping, to allow EJBs, Servlets and JSPs to invoke CORBA objects (potentially non-Java objects)
V
A very high-performance robust implementation of IIOP, which has become the de-facto industry standard IIOP protocol implementation against which other IIOP implementations are judged
V
GIOP 1.2 for enhanced interoperability. Fragmentation for enhanced performance by enabling large requests to be interleaved seamlessly with smaller ones. 
V
Asynchronous and deferred synchronous invocations on EJBs supported using CORBA Dynamic Invocation Interface (DII)
V
Callbacks and recursive calls supported amongst EJBs, Servlets, JSP, and Applets, using CORBA- or RMI-style interfaces, without middleware-level deadlocks, and navigating firewalls using the Gatekeeper
V
Pluggable transport layers to allow OEM customers to add custom transport layers
V
Ability to invoke CORBA objects from EJBs, while preserving transaction and security contexts
V
Ability for CORBA clients to invoke EJBs, while preserving transaction and security contexts
V
RMI over IIOP & Java-to-IDL Mapping  
Supports the CORBA 2.3 Java-to-IDL Mapping
V
Merges RMI and CORBA… allows user-friendly RMI-style APIs for building distributed applications, with an enterprise-quality object messaging protocol (IIOP) underneath
V
Supports RMI interfaces for client interfaces and server implementations
V
Pure Java 2 implementation (no native code)
V
Integrated Java Web Server with Servlets and JSP  
Implemented completely in 100% Pure Java, for maximum portability
V
Support for the latest versions of the Servlet API, provides limitless opportunities for dynamic web sites and integration with server component models such as EJB
V
Support for the latest versions of JSP, to allow developers to freely embed Java code in HTML files in powerful ways, to invoke EJBs, access databases, etc.
V
On-the-fly Page Compilation, to increase the performance of Java code embedded in HTML files
V
Session Tracking, for building sophisticated stateful models above the web’s stateless protocols
V
Presentation Templates allow separation of HTML content from overall look and feel
V
Digital signatures, to authenticate clients and servers
V
Simplified administration for web sites and servers, provide a single point of control for installing, tuning and managing a complex web site
V
On-the-fly web server configuration, allows administrators to change user groups and make security modifications without having to restart the web server, a big plus for organizations where every second of downtime can mean the loss of hundreds of hits
V
Real-time monitoring of resource usage, with a variety of useful reports and charts
V
Ability to colocate the web server and servlet engine in one process, to increase performance
V
Ability to deploy the web server and servlet engine on separate machines, to manage server resources
V
Support for Virtual Hosts, to allow hosting multiple web sites on the same machine
V
Version Viewing for each container, to inform the administrator of the version & short description of the container, version of the application server software running the container, name & IP address of host machine, the Java Virtual Machine version being used, Classpath specifications for the container, and JDBC drivers being used by the container 
V
Environment Viewer for each container, to display the environment variables that the container is running with
V
View Performance Information for each container as bar charts, line charts, 3-D graphs, Pie charts, or numbers
V
View Memory Usage Information, to monitor the amount of memory used or available at any point in time, or maximum memory used or available for a given timeframe
V
Bean State panel provides an overview of an enterprise bean’s lifecycle and the proportion of time a bean spends in each phase, useful for troubleshooting performance problems – information can be viewed as pie charts, line charts, or flow diagrams.
V
Integration with Popular Web Servers and Servlet Engines  
Apache Web Server
V
Netscape Enterprise Server & FastTrack Server
V
Microsoft Internet Information Server (IIS)
V
Allaire JRun Servlet Engine
V
Apache JServ Servlet Engine
V
Distributed Transactions (JTS/JTA)  
Complete implementation of the OMG Object Transaction Service (OTS) specification
V
First complete implementation of the Java Transaction Service (JTS) with 2-phase-commit
V
Automatic 1-phase commit optimization where appropriate, to avoid the overhead of XA wherever possible
V
Multiple beans in multiple containers can be involved in one logical transaction
V
Multiple containers and multiple heterogeneous databases can be involved in one logical transaction
V
CORBA servers written in multiple languages and EJB containers can all participate in the same logical transaction
V
Ability to run as a lightweight in-process transaction service specific to one container, or as a distributed enterprise-wide 2-phase-commit transaction service
V
First implementation built from the ground-up as an object-oriented CORBA based OTS/JTS implementation (as opposed to being layered on top of older TP monitors) 
V
Allows the development of transactional servers both in Java & in C++
V
Built-in database connection pooling to manage server and database resources
V
Automatic association of OTS transaction with database connection to enable coordination of transactions
V
Support for optimized local transactions as encouraged in the EJB spec
V
Support for driving legacy systems such as CICS, IMS, Tuxedo, MQSeries, etc.
V
Support for driving, and being driven by, another OMG OTS-compliant transaction manager
V
Easily integrated with any XA-compliant resource or JDBC2 resource to participate in distributed transactions
V
Highest-performing OTS implementation among the three leading OTS products
V
EJBs or EJB Clients can explicitly originate and orchestrate distributed transactions using JTS APIs
V
IAS4 Container can automatically coordinate transactions
V
Pseudo-2-phase-commit optimization flag available, to obtain 99% of the benefit of 2 phase commit, without paying for 100% recoverability
V
JNDI Naming Service  
Support for JNDI APIs, implemented as a CosNaming Provider for JNDI, to allow RMI- or EJB-style clients to look up objects in the same naming services being used by CORBA clients & servers
V
Support for OMG-standard CORBA Naming Service APIs
V
Support for using an industry standard LDAP server as your directory service (see Pluggable Storage, below), and inherit enterprise-level scalability, replication, and fault-tolerance offered by commercial LDAP servers, such as the Netscape Directory Server
V
Multiple naming servers can be started for the same naming data store for replication, performance and scalability
V
Support for the Interoperable Naming Service (INS) Specification, which allows IAS4’s Naming Service to be integrated into any CORBA application with ease
V
Pluggable Storage in the Naming Service  
Several different kinds of storage can be “plugged in” underneath the Naming Service
V
In-Memory Storage, to be used when it is reasonable to keep all naming data in memory, and does not need to be persistent
V
JNDI Storage, to allow naming data to be written to any directory service for which there exists a JNDI provider, e.g., LDAP, NDS, Active Directory, etc.
V
JDBC Storage to allow naming data to be written to any database for which there exists a JDBC driver, e.g., Oracle, Sybase, MS SQL Server, DB2, JDataStore, InterBase
V
Optimized JDBC adaptor with caching facility, to bring the performance of using a JDBC data store for naming data, close to the performance of using an In-Memory storage.
V
Direct DataExpress Adaptor, for fast access to the Inprise’s JDataStore 
V
Federation Support in the Naming Service  
Support for federation, to allow multiple naming servers to be deployed, with naming hierarchies spanning multiple servers, which can increase performance and scalability, and allow decentralized administration
V
Command-line options for federation of naming servers, for easily federating multiple naming servers
V
Clustering in the Naming Service  
Ability to associate a single service name with multiple EJB object references, which allows the Naming Service to load-balance over the set, when a client attempts to look up that name
V
Requires no changes to client code performing lookups of object references
V
Multiple EJB clusters can be created in the Naming Service, to allow multiple unrelated services to use the clustering feature
V
Criterion for load-balancing is specified for each cluster, to allow different clusters to use different load-balancing criteria
V
APIs to create clusters, and add, remove and iterate through their members, for complete programmatic control over clusters
V
APIs to retrieve all the clusters that exist in the Naming Service, to allow clients, servers and admin tools to determine which service clusters exist
V
Load-Balancing Support in the Naming Service  
Dynamic Load-Balancing is performed automatically, both by the Smart Agent (see Smart Agent) and by the Naming Service
V
Customizable Load-Balancing Algorithms, can be plugged into the Naming Service using the Criterion Manager APIs, or into clients using the BindInterceptor APIs
V
Load balancing at the EJB object level can be combined with load balancing at the DNS, web server, or servlet engine level
V
Fault-Tolerance and Fail-Over in the Naming Service  
Failover of the Naming Service, avoids a single point of failure at the Naming Service by allowing administrators to identify master and slave naming servers
V
Transparent failover by clients from a failed master Naming Server to a slave Naming Server, with no special coding required by application programmer, to avoid single point of failure at the Naming Service
V
Transparent failover by clients from a failed member of cluster to another member of that cluster, with no special coding required by the application programmer, to tolerate a failure in EJB objects or containers
V
Built-in Scalability  
Ability to replicate EJBs in multiple containers on multiple machines
V
Efficient Thread Pooling built-in, to manage server resources in a scalable fashion
V
Client-to-Container Connection Pooling built-in, to manage TCP/IP connections in a scalable fashion
V
Database Connection Pooling built-in for all data access (BMP, CMP, Session Beans, Servlets, JSPs, or any other client), to manage database connections in a scalable fashion
V
Same-process Optimizations during method invocations, to boost performance for targets that are in the local process (e.g., substituting remote object references with local pointers/references)
V
Same-process copying of EJB arguments (as described in the EJB spec) configurable on a bean-by-bean basis
V
Use of sophisticated server adaptation layer (POA) allows for great scalability and maps well to EJB object pooling guidelines
V
Optimized client-side support for multi-threading to allow multiple threads in a client process to make simultaneous invocations to the same server, using a single connection, without blocking or deadlocking
V
Ability to deploy the EJB container, web server and servlet engine all collocated in one process, or all in separate processes and machines, to manage server resources as appropriate
V
Ability to run the EJB container as part of your own Java application where you write the main(), to allow complete flexibility in the partitioning of your application
V
Scalable Connection Management  
Connection Management enables EJB Containers to recycle existing connections for maximum performance, scalability, and throughput.
V
Ability for an EJB Container programmer or administrator to specify the maximum number of client connections that can be open at any point in time
V
Ability for a client programmer or administrator to specify the maximum number of server connections that can be open at any point in time
V
Connection idle-timeouts allow EJB client and server runtimes to transparently shut down TCP/IP connections that are not being used
V
Connection recycling, in which the EJB Container runtime automatically shuts down the Least Recently Used connection to allow a new client to connect to the server, without exceeding the maximum number of allowed connections
V
Automatic reestablishment of a previously-terminated connection between a client and a container when it is needed again, without disrupting the client-server session
V
Pluggable connection management models to allow OEM customers to add custom connection management algorithms
V
Gatekeeper  
The Gatekeeper is a high-performance IIOP Proxy based on CORBA Firewall specifications, which allows invocations from CORBA/EJB clients to traverse firewalls (according to administrator specifications) on their way to the target EJBs or CORBA objects
V
Configurable stateless/stateful connection management for flexibility in managing server resources
V
Ability to handle asynchronous IIOP in addition to synchronous IIOP
V
Clustering, the ability to cluster multiple gatekeepers and transparently load balance across them
V
Fault tolerance, to allow defining master and slave gatekeepers and transparent fail-over across them
V
Support for all popular firewall products and configurations, from simple dual-homed machines and software based firewalls, to sophisticated configurations with multiple levels of routers, demilitarized zones (DMZs) and bastion hosts
V
Support for Network Address Translation (NAT) devices, which substitute one IP address for another for security purposes, and cause havoc in other ORBs
V
Support for Dual-Homed Gateway machines which are often used to run software-based firewalls
V
Gatekeeper Chaining, useful not only for navigating multiple levels of firewalls but also for concentrating connections from large numbers of clients
V
Support for HTTP Proxy Servers, which allows clients behind proxy servers to interact with the gatekeeper without problems
V
Support for SOCKS, which allows Java clients running behind SOCKS proxy servers to make IIOP invocations 
V
Support for HTTP Tunneling, which allows clients to tunnel IIOP over HTTP, to ease deployment
V
Seamless integration with web servers and servlet engines
V
Applet Support:
V
-- Lightweight HTTP server built-in, for serving applets or serving HTML on small-scale
V
-- Support for making IIOP callback to applets, in the presence of firewalls
V
-- Support for forwarding an Applet’s requests for communication with a Smart Agent, to the Smart Agent network on the server-side, to avoid UDP communication on the Internet and WANs
V
Visual Management and Administration Tools  
Both HTML-based and Java-based Visual GUI tools for simplified administration
V
Visual control of containers and their properties using the VisiBroker Console
V
Discover all running EJB Containers on all machines and browse their contents
V
Setup, discover, monitor and tune all web services
V
Servlet administration, for loading/unloading servlets, configuring Servlet parameters, specifying Servlet aliases, etc.
V
Discover all JAR files that have been deployed to each container and browse their contents
V
Discover all running Naming Services and browse their contents
V
Support for browsing & editing any naming service supporting JNDI
V
Discover all running Gatekeepers and configure their properties
V
Discover all running Transaction Services and browse the current and completed transactions using filters
V
Remote EJB Deployment, to allow deploying/undeploying/redeploying EJBs to remote containers
V
Dynamic Hot-Deploy, to deploy/undeploy/redeploy EJBs to containers without shutting down or restarting containers
V
Ability to monitor all runtime aspects of EJBs and containers, using AppCenter
V
Ability to trace all database calls and SQL statements made by Container Managed Persistence, for database-related debugging and performance tuning
V
XML Deployment Descriptor Editor, to interactively choose data sources and intelligently edit transaction attributes and isolation levels, security attributes, JNDI names, Bean Type information, Bean properties, and CMP properties
V
Ability to view and manage log files of services
V
Uniform Management of EJB/ORB communication & resource management parameters  
Ability to configure all configuration properties using a uniform naming convention via the command line
V
Ability to configure all configuration properties using a uniform naming convention via a centralized properties file
V
Ability to configure all configuration properties using a uniform naming convention via programmatic APIs
V
Auto-bootstrapping with Integrated VisiBroker SmartAgent   
A VisiBroker value-add that provides a dynamic distributed bootstrapping service with built-in fault-tolerance and load-balancing
V
Support for automatically discovering EJB services such as EJB containers, the Naming Service, the Integrated Transaction Service (ITS), etc.
V
Support for automatic discovery of the nearest Smart Agent by EJB containers
V
Support for automatic discovery of the nearest Smart Agent by EJB client processes
V
Ability for Smart Agents to discover other Smart Agents in the network
V
Ability to control whether and when UDP broadcasts are used to automatically discover Smart Agents
V
Support for networks of Smart Agents to span subnets
V
Enables High Availability & Fault Tolerance, to allow a EJB client using an EJB E in container C on machine M to transparently fail over to using a replica, EJB F in container D on machine N, without requiring any coding by the application programmer
V
Round-robin load balancing built-in
V
ORB hooks (bind interceptors) and programming examples for adding other load-balancing algorithms
V
Support for standard CORBA/EJB object migration, which allows clients to automatically discover that an EJB has moved to a different machine or container without requiring special coding by the application programmer
V
Support for the use of Smart Agents in Internet or other Wide Area Network (WAN) scenarios when used in conjunction with the Gatekeeper
V
Ability for an administrator to turn off the failover feature for a client, but leave other Smart Agent related behaviors intact
V
Ability to disable and completely remove the Smart Agent from your deployed application. (The Smart Agent can be intelligently leveraged by all other parts of IAS4, but is not required to be present).
V
Ability to create multiple parallel “virtual domains” of EJB clients, EJBs, and containers on the same set of machines (e.g., development vs. QA), by using different Smart Agent port numbers
V
Ability to run as an NT Service when running on Windows NT
V
Utilities for Packaging and Deployment  
Command-line and graphical utilities for packaging EJBs into Jar files
V
Graphical utilities for creating XML deployment descriptors (see Visual Tools)
V
Command-line and graphical utilities for verifying the contents of Jar files for compliance with the EJB 1.1 specification, and IAS4
V
IAS4-specific XML DTD for IAS4-specific configuration in the separate deployment descriptor, as encouraged by the EJB specification
V
Command-line tool for converting EJB 1.0 (Java Serialized) deployment descriptors to EJB 1.1 XML-based deployment descriptors
V
Bundled Borland JDataStore 100% Pure Java SQL92 RDBMS  
Pure Java JDataStore for high performance data caching and compact persistence of data, objects, and arbitrary files.
V
Ease-of-use and complete out-of-the-box experience, because all EJB development can be done with JDataStore, and later retargeted for Oracle/Sybase/Informix/DB2/etc.
V
JDataStore SQL-92 Query engine
V
JDataStore transaction and crash recovery support
V
Advanced concurrency control to increase application performance
V
JDataStore JDBC 2.0 Type-4 drivers (local and remote)
V
JDataStore Explorer for visually managing JDataStores
V
Platform Availability  
JDK 1.2.2 on the following platforms:
V
Microsoft Windows NT
V
Sun Solaris
V
IBM AIX
V
HP-UX
V

 
 
 
 
 

Separately Available Options for IAS4
 
Complete range of CORBA Services (from Prism Technologies)      
OpenFusion Trading Service 
V
    
OpenFusion Notification Service 
V
    
OpenFusion LifeCycle Service
V
    
OpenFusion Property Service
V
    
OpenFusion Collection Service 
V
    
OpenFusion Concurrency Service 
V
    
OpenFusion Relationship Service 
V
    
OpenFusion Time Service 
V
    
OPTIONAL Gatekeeper Features (with Inprise Security Service):      
Support for deploying Gatekeeper functionality as a Servlet, which allows gatekeeper functionality to be tightly integrated with your enterprise web server or servlet engine, and simplified administration and management
V
    
Support for IIOP-over-SSL, which layers IIOP traffic over SSL, thus automatically encrypting all CORBA traffic between a given client and server, without requiring coding changes
V
    
Support for choosing IIOP-over-SLL or unencrypted IIOP, from the Gatekeeper to each server, on a server-by-server basis
V
    
Support for HTTPS Tunneling, which allows thin clients to tunnel IIOP over HTTPS – by taking advantage of the HTTPS implementation already available in all popular web browsers, this feature makes possible secure CORBA clients with zero-installation and dramatically eases deployment of secure CORBA applications
V
    
Supports IIOP/SSL Callbacks, to allow servers to make secure CORBA invocations to clients
V
    
Credential Forwarding, the ability to forward client credentials to servers, so that servers can authenticate clients themselves
V
    
Authentication of clients on behalf of servers to allow the Gatekeeper to immediately reject intruders
V
    

Interface Ltd.

Tel: 7+(095) 135-55-00, 135-25-19
E-mail: mail@interface.ru
http://www.interface.ru
Ďîäăîňîâčëč: tkachev@interface.ru
Äŕňŕ: 17.11.99