The answer you gave me for the second question (option A) kinda resolved the third question also. There have to be two databases if the older system cannot be touched and should work as is (perl/cgi + html + oracle).
Last but not the least, thanks again for all the responses.
Originally posted by Ricardo Ferreira:
Hi,
First, i�ve to tell you that, any this questions you have posted here, must be evaluated for you, as your point of view. I think that, the nature of the certification, is test you in, how can you create an solution for a given problem. Try to create your own solutions ok ? Well, here we go.
----------------------------------------------------------------------------
1) Does the new travel agent java application have to be Java Swing? If it is Swing then what protocol would it use to communicate with the business tier (EJBs). IIOP right?
R = There are many ways to connect to the business tier. If you expose your business tier, using ejb�s, the only protocol to use is, RMI-IIOP. But, it�s not the only way. Supose that you create an fa�ade for a group of use cases (an boundaire), and expose this fa�ade (SLSB) as an web service. So, you could access it using HTTP or HTTPS over SOAP. As an architect, choose one that relies with the Customer needs.
2) Requirements say that I should provide access to the mileage system content via the web to the customers. But there already is a web-based mileage system written in perl/cgi + html + oracle.
a) Should I use that existing system and expose it to the customers?
OR
b) Do they need a unified view that combines booking system and mileage system into one web based UI for customers.
The latter option means that I have to re-write the mileage system front end also.
R = Again ... There are too many ways for doing that. One of this solutions is, access the mileage directly using JDBC, since the database is Oracle (and you realize that oracle provides an JCA connector). Another approach could be, create an interface with the Perl/CGI system, using HTTP processing, as URL rewrite or HTTP headers parsers. I preffer the first method and one more thing: Don�t forget that, FBN CEO said that: "I don�t intend to rewrite the mileage system now, since i�ve invested a half million dollars". If you even think in rewrite the system, this is an explicity case that an architect don�t fixing the customer expectations. Keep the "A" alternative in mind, that�s what the assignment wants.
3) Mileage system already has data sitting on an oracle database. The new booking system re-write replaces the old IMS database with a new oracle database. Can I use the mileage system's oracle database instance for the new booking system by creating a new schema possibly? Or by creating additional tables in the same schema! I will definitely avoid the cost of talking to two databases!
R = The database company�s topology don�t need to be measured in the project. You just have to create an way to access the legacy system.
Never forgets: Meet the customers neeeds! Is the key for the SCEA !
Best Regards,