JCAPS = Nonsense (at least here)
Come hell or high water - this company is hell bent on including JCAPS as part of it's enterprise architecture, even though it doesn't plan to use any of the features that might set it apart from it competitors or open source alternatives.
The long-term plan here is for the business users to use a BPMN-compliant tool (not the one from JCAPS) to create the business processes.
These processes will integrate web service calls, creating a sort of business mashup of these services. The services will be written in .Net, not JCAPS.
The only place JCAPS enters the equation is as the platform to run the BPEL generated from the BPMN. Make any sense? Not to me. Isn't a BPEL engine included in Glassfish? I'm sure this is just one of several free or low cost alternatives to execute BPEL.
What I can't figure out is this company's infatuation with JCAPS. Given the shortcomings they've encountered already, why they are so intent on looking for more places to implement this technology stack?
The long-term plan here is for the business users to use a BPMN-compliant tool (not the one from JCAPS) to create the business processes.
These processes will integrate web service calls, creating a sort of business mashup of these services. The services will be written in .Net, not JCAPS.
The only place JCAPS enters the equation is as the platform to run the BPEL generated from the BPMN. Make any sense? Not to me. Isn't a BPEL engine included in Glassfish? I'm sure this is just one of several free or low cost alternatives to execute BPEL.
What I can't figure out is this company's infatuation with JCAPS. Given the shortcomings they've encountered already, why they are so intent on looking for more places to implement this technology stack?
Comments