Question:

We are currently running client server applications using Dev 6i on Windows platform and are planning for a switch to 9i or 10g but are a little reluctant in doing so, as we are facing lot of problems in the test environment especially with iAS.

My question is I want to migrate on a LAN environment to 9i or 10g. How do I do it without going into the complications of configuring infrastructure?

The main issue faced by us is iAS configuration … the services will be shutting down without any specific reason. We applied the right patches but instead of improvement in the configuration we faced more problems. We really don't need the web-based architecture at the moment but want to move to 9i or 10g, how do we do it?

The other issue moving to iAS are the resources required. We really cannot figure out the hardware requirements because we noticed that the performance of the applications with just few forms is dead slow with a configuration of around 2 GB of RAM. Another issue we came across is the Report Security with HTML reports. Users can make their own changes on the browser and reprint a report. Whereas in 6i users had no control of their reports. How do I handle a situation like this?

If we are moving to a Web Based Environment how do we go about training our staff who are new to Java or Web based tools?

If possible please provide me details as to what exactly is the hardware configuration required for iAS. I have a say regarding in-house developed financial application alongside with other applications. With around 80 - 100 forms, similar number of Reports with 45 -50 users.
 

This question posed on 09 August 2005

Answer:

Wow, that is a lot of questions. First, the move from 6i to 9i is the difficult move, while 9i to 10g is minor. Therefore, my recommendation is go to AS10g as it is easier to install, manage, and maintain.

That said, the hardware issue is a tough one. I have installed the infrastructure, middle tier and back end database on one windows server with 2 x 2.8 CPU and 4G ram and it worked very well for a rather small (70-100) company. However, if the server is overloaded, you have no choice but to add servers and off load some of the tasks. If you only have two servers, then normally you would move the back end database to a
separate server. If you have three servers you can split the
infrastructure and middle tier but you might get better performance by placing the web cache on its own server in front.

Bottom line, the application server is designed to be spread across multiple small servers and your application determines how well a set of servers handles the load you place on it. The real advantage of the application server is that you can easily add additional middle tiers and the AS will handle the load balancing and fail over.

As far as the minimum hardware configuration, that is explained in the docs but the minimum hardly ever will handle the load.