Enterprise Application Re-engineering Study

Technology is developing, requirement of the business is changing, as a result, the applications should also update. That is why the concept reengineering originates in the software engineering.Reengineering consists by three basic activities, reverse engineering, refactoring and forward engineering. During the process, it also needs to consider how to make the new application compliant with the legacy system, or how to reuse some modules of the application. Refer to forward engineering, the implementation includes evolutionary model, incremental model and explosive model, the choice depends on the target platform and technology requirement.There would be extra characters when try to reengineering on the enterprise system, usually, the exploding way is selected when using J2EE to forward engineering, which relatively harder. You need to use these well-rounded enterprise technology, e.g. JMS MOM, Websphere Application server, which then can provide a continuous development;secondly, to pursue the extreme performance, it need to find the bottleneck of the system and eliminate with refactoring.The experience of reengineering on the messaging centralized system make us to realize that a framework based on JMS with high performance and communication reliability really become a universal requirement. So this paper will introduce how we fall to developing such a framework.The framework is oriented to the distributed server, the features including: 1, after building the pipeline, messaging on it will be guaranteed both sequence and reliability since the mechanism of sequence and acknowledge managing underlying;2, the message submit to upper layer on the server side, it can use a local transaction to process the message, which leads to good performance, since it will get the message even if the transaction is failed;3, on starting server after some fail over occurred, all these pipelines can be rebuilt automatically, and the messages fail to transfer during that period will also be guaranteed by the underlying protocol.