what is tiera back office server?
tiera back office server (tbos) is a multithreaded
application server development system. tbos allows developers to take
existing 2-tier (client-server) java applications, applets, beans,
ejb beans and c/c++ code and re-deploy them in a multi-tier distributed
environment. tbos insulates the developer from the complexity of building
distributed transaction-based systems. this allows developers to focus
on building the business logic only and not building the entire server
infrastructure, decreasing the time-to-market and risk for building
these types of systems.
tbos automatically adds thread,
session, memory, console, log, performance, jdbc connection, transaction
and system management capabilities to the developed business process
objects. the developed applications are specifically designed for e-commerce
and mobile applications.
tbos is a natively compiled
container that houses the business process objects written in java and
c++. tbos can be extended to add business process objects in any
language. the tbos server is a high performance, highly scalable, distributed,
transaction based and secure system.
the tbos is accessed from an
"extremely thin" client . tbos client applications can be written in
java or c++. tbos client applications can run on windows (95,98,
nt and 2000) and any java enabled platform, including hand held devices.
tbos provides an object browser to dynamically create, manipulate and
destroy tbos business process objects, so that developers and administrators
can easily view objects under tbos�s control.
tbos uses a repository to help
the developers and system administrators keep a complete inventory of
all tbos business process objects and server configurations. administrators
use the repository to define security policies for all business process
objects that have been imported into the repository. the entire develoment,
administration, and deployment environments are completely graphically
tbos is an open system that
inter-operates with corba and com architectures and can utilize corba
and com services.
tbos has a centralized management console that provides a global view
of all tbos severs deployed through the enterprise.
tbos can managed by network management systems such as hp openview,
ca-unicenter, and tivoli.
why would you use tbos?
the founders of tiera had spent several
years evaluating and building industrial strength e-commerce applications
and came across some serious problems using existing "out of the box"
technology. below are just a few.
- the existing technology of building web
sites (cgi, active server pages, etc) were very easy to implement,
but were no more than client server applications. these applications
would not scale to thousands of users. they were not transaction based.
- the newer technology alternatives, such as
corba, are extremely complex and very unstable. there is not a lot
of people in the workforce that know how to effectively use this new
technology. it also was unlikely, due to very slow industry adoption,
that this situation would radically change in the upcoming years.
also, these newer technology alternatives had limited integration
with existing back office systems. you almost have start from scratch.
- these new technology alternatives, were very
expensive to deploy. the more popular orb vendors require a lot of
capital investment for development seats, and want a percentage of
the value of the deployed product. it is not good business sense to
agree to this type of arrangement. why would anybody want to give
up a significant percentage of your revenue for a piece of middleware
that adds very little value to the end deliverable. it might provide
technical value, but not much business value to the end buyer.
- most technology choices were incomplete.
they did not have all the capabilities that were required to deploy
the system in a production environment.
this prompted the founders to build a comprehensive
server technology that was based on the following requirements.
who would use tbos?
- the developer should not be concerned
with the complexity of building distributed applications for the internet.
they should be focused on solving the business's problems, not building
the infrastructure. since the majority of the required infrastructure
is the same for almost all applications, it should be built
- companies should be able to use their existing
staff to build these applications. they should not have to employ
a large additional staff to build these new systems, even if they
could find them.
- the system should be able to easily integrate
existing back office systems. not only the data, but the applications
that house the logic that process the data as well.
- the system should be a completely maintainable
and manageable production level system.
- the system should be able to inter-operate
with other systems based on industry standards
companies wanting to preserve their current
investment in existing 2-tier client-server systems developed in java,
c/c++, and other legacy languages and deploy them on the intranet, internet,
or hand held devices without re-writing them in their entirety.
- companies building new systems that are
looking for maximum scalability of their system, where the system
is based on java, c++, xml business objects and thin clients and then
deploy them on the intranet, internet, or hand held devices.
- companies that have existing products that
they would like to extend by add java/c++ business objects/scripting
to their product.
- companies that have existing products that
they would like internet enable, without having to re-write them from
- companies who need to quickly build industrial
strength intranet, internet, or hand held device applications, but
do not have the core competency in java, corba, distributed transactions,