This week's book giveaway is in the OCPJP forum.
We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes Migration of Application to Java Platform need help Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Migration of Application to Java Platform need help" Watch "Migration of Application to Java Platform need help" New topic
Author

Migration of Application to Java Platform need help

Jasmine kaur
Ranch Hand

Joined: Nov 25, 2003
Posts: 160
Hi All,

I need help to guide me as we are migrating a documentum application to java platform. This application is an intranet application
which handles IT request related to software and hardware queries. Please assist me to design the workflow for thier business logic for thier IT request ticket raising flow. What are the best ways to design workflow in java so that appplication can migrate well on java platform. We are using JSF at UI level and this application is for 3000 users.

Thanks in adavance.


jasmine kaur
devendra bargujar
Greenhorn

Joined: Feb 10, 2010
Posts: 4
Hello Jasmine -

Not sure why you call it migration becuase from below problem statements "to me" it seems that documentum applciation is being replaced by new application build on JAVA technology...

First and for most realize your workflow DESIGN using some UML tool.

TIPS
1) First and more most you need to have some ADMIN related DB tables which will HOLD all email ID's which will be used once request/ticket is raised. You can provide access to these tables on ROLE basis from same GUI (JSF)..!
2) Design your data base first rather then JAVA workflow. Becuase by this step you will identify ENTITIES and their ATTRIBUTES.
3) As state of request/ticket is not necessary to maintain. So you can go for simple JAVA classes (Helper classes) rather then EJB's with proper designated purpose and roles. As per my suggestion workflow state should be maintained into DB and simple THREAD apprach could be used for solving TIMING related constraints.

Hope above tips help you....

Regards... Devendra
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Migration of Application to Java Platform need help