IBAS GBF - Global Banking Factory is a new solution designed and developed on the latest technology (100% Java, object-oriented and on a Service Oriented Architecture – SOA) which has unprecedented flexibility and openness through its true component-based design.
Its functionality is based on a single core system using a series of integrated common tables, rules and objects, and presented through a graphical user interface. It is fully component-based and object-oriented and has been designed and developed, from the outset, as a real global package solution, for fast implementation and without the need for programming to meet every client’s specific requirements.
Using parameters and rules, the system can easily be adapted to meet the bank’s requisite functionality. This is all done without the system being compromised. Fully assembled, the objects and the components form a complete and stable banking solution. Individually, the objects and the components replace and modernise, saving costs and preparing for the future.
The inherent flexibility of IBAS GBF means banks can rapidly tailor it to meet their current needs and can keep pace with all future requirements, bringing a competitive edge plus reduced overheads from improved straight-through processing.
IBAS GBF is one of few banking systems on the market today that is modular and, at the same time, a fully integrated package solution. It is proven in live sites and spans a broad range of areas, including: payments, trade finance, financing and loans, forex & MM, invoicing, factoring, and account management, as a global package.
Combine the innovation, flexibility and technology of IBAS GBF with our delivery track-record and levels of customer satisfaction – we believe these are some of the reasons that set us apart in today’s market.
Imagine a world where programs could run on any processor without the need to rewrite or compile a single line; a world where programs did not crash due to stray memory references; a programming language that was modular enough to allow true code reusability; a language that supported multi-threading. Java does all of this. IBAS is developed in 100% Java.
From a technical perspective, the flexibility means the IBAS system is independent of language, operating systems, database, hardware and delivery channel. It only requires the installation of a Java Virtual Machine (JVM) to facilitate the IBAS Application Server and web-based User Interfaces. An optional web server can be installed to facilitate access to the Java Applets and HTML documents.
IBAS Systems are currently installed in a number of countries, on different hardware platforms, such as IBM, Oracle and VMWare.
IBAS GBF is designed and implemented in a multi-layer architecture. The clients are thin and can be run either through a WEB Browser or as a Java application (both configurations are possible, even towards the same system, without any modifications to the system).
The IBAS Application Server contains a variety of services responsible for business logic, data access and manipulation, interfaces to other systems, etc. The IBAS Application Server can be run on one or several computers depending on the preferred level of fault tolerance and load balancing.
IBAS GBF utilises standard Java features such as Java Foundation Classes (Swing) for the GUI, Remote Method Invocation (RMI) for communication between processes, Java Database Connectivity (JDBC) for Data Access & Manipulation, etc. Eclipse is used as our Integrated Development Environment in addition to CBA’s own Development Tools which include: IBAS Visual Designer Tools and the IBAS Frame Design System.
IBAS itself consists of several “development tools and objects” which can be used by the customer bank’s IT team to customise and adapt the systems to fit the business critical requirements.
Since IBAS GBF is developed in 100% pure Java the system is independent of the hardware platform. For the Application Server the only requirement is that there is a Java (JVM) and a JDBC driver available on that specific platform. On the clients a WEB Browser supporting Java (JVM) must be available. In addition a WEB Browser is needed to store help documents (HTML) and some initial Java classes (if the clients are to be started through a WEB Browser).
IBAS GBF use Java Database Connectivity (JDBC) to access the RDBMS. As RDBMS, current IBAS customers use Oracle or Microsoft SQL*Server. Standard reporting tools may be purchased by the Bank to ”develop” the necessary reporting facilities without involving large development projects and external resources. Other databases systems, such as IBM DB2 and MySQL may also be offered for use with the IBAS systems.
IBAS databases are updated on-line in real-time from the relevant IBAS Applications. The IBAS systems can also work in batch mode to save time, maximise performance and get the most out of the hardware, but it is the customer bank that determines which operations are performed on-line or in batch mode.
IBAS contains its own security systems, based on user roles and has also been interfaced with both Smart Cards and Digital Certificates.
Interfacing and Messaging
IBAS GBF allows financial institutions to easily integrate with existing systems in order to share data in a secure, accurate, and highly cost-effective way across processes, protocols and standards, and on a single platform. As a single central platform, IBAS GBF ensures that systems are capable of reciprocal operation and protect the bank's legacy applications.
As banks look to improve their financial position and reduce risk exposure, they need to optimise their operations across multiple product areas and in multiple countries. IBAS GBF is helping these customers to transform their operations into integrated, cost-effective systems that drive operational efficiency.
XML is used for exchanging data within the IBAS GBF systems, and can also be used for exchanging data with external systems. IBM Websphere MQ can be used as the communication layer. IBAS GBF uses either AFT, MQSA or MQHA towards SWIFTAlliance. In addition, JMS and WBI are alternatives used for interfaces and messaging.