JAVA Framework Environment (SOA)

Deliverable 1 – Java Environment Setup and Samples XXXXXXXXXXXXXXX Download and install each of the 4 sections (Dev, portal, business, and Data) applications. In the Development Environment Server (details to follow) get the following examples complied, and deployed using Maven2 and Ivy (please see detailed instructions) a)Spring 3 Petshop clinic using PostgreSQL as database's [login to view URL] and deploy on Jboss AS b)Spring Integration Coffee shop example using ActiveMQ and Test harness. [login to view URL] c)Create Pet Clinic Owner from Queue – submit SOAP message for createpetclinicowner to activeMQ via activeMQ web-based test harness which will create a record in the database via the Sprint pojo Deliverable 2 – Common Business Application Framework XXXXXXXXXXXXXXX We will create a simple service “Sales Lead Portlet Options WSDL” that will update user preferences and have 5 operations. This is a common core for building business applications based on the Spring Framework. The application framework will have a Web Service API for the sample Portal application to consume. All business processing will be based on plain old java objects (pojo) business objects which receive information from the enterprise service bus or the local Database accessed through hibernate mappings to a PostgreSQL Database. Common Services will be the following: [login to view URL] Error Handling Based on the common Status Info business object [login to view URL] logging and configuration of each deployed business applications [login to view URL] registration of each business applications Deliverable 3 – Data Access Layer (Database and message queue) XXXXXXXXXXXXXXX This is a common core for persistence of data, and access to data from the system. There are two main areas for data access. Please see this tutorial for basics in Spring 2.5 but most concepts are the same in 3.0 [login to view URL] AND Hibernate and postgreSQL are located here also. Part 1 – Database The database will house the data for the Sales Lead Portlet Options. This database will have 5 tables (see design below). We need to create the following sql scripts to be supported via ant/Ivy [login to view URL], [login to view URL], [login to view URL], [login to view URL], 5.drop_tables.sql. Part 2 – Message Queue The will need to be an Active MQ deployed with the following Queue Structures CompanyTest1_SalesPortal_Send CompanyTest1_SalesPortal_Receive CompanyTest1_SalesPortal_Error CompanyTest1_SalesPortal_DLQ. Deliverable 4 – Common Portal Application Framework XXXXXXXXXXXXXXX A common Portal framework will be developed to be used for a baseline for all future Portlets. This will include the following projects to be integrated and deployed on the J-Boss Portal Server. Framework products will include: Framework functionality: [login to view URL] and style sheet per company based on login. This is a hosted multi company application. [login to view URL] – User login, groups and roles based on Jboss (LDAP will be later) [login to view URL] logging for each product, such as log location, format, viewer, rolling settings and configurations [login to view URL] error handling – based on a common Status Info object and will include common error messages, configuration, and deployment [login to view URL] will create a Sample Portlet to be deployed through Jboss Admin to support the presentation of the Sales Lead Options Page. User of CompanyTest1 and CompanyTest2 Can Login to Application to see the new Portlet Deployed and can create, Update, Read, and Delete Values.