• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Migration of Application to Java Platform need help

 
Ranch Hand
Posts: 160
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
reply
    Bookmark Topic Watch Topic
  • New Topic