This topic has not yet been written. The content below is from the topic description.
ConfiguRed seRViCes WebLogic Server has the concept of deployed applications and configured services. Services — in WLS terminology — can include JDBC services and JMS destinations, which are considered deployable artifacts in JBoss. This leads to two very distinct models: With Wls, services such as JDBC and JMS are configured through the administration console by the WebLogic administrator. This is true in both production and development, though the developer may also be acting as the WLS administrator in a developer environment. While such service configuration ultimately depends on application needs, it is both physically and practically separate from the application itself. Application developers often document their service dependencies and administrators follow the document to set up the required services for the application to function properly. Red Hat Consulting Strategic Migration Planning Guide8 www.jboss.com With Jboss, each service (for example, a JDBC connection pool or a JMS queue) is configured in its own XML file. Two or more services of the same type can often be configured in the same XML file, if that is preferable. This gives users flexibility in their configuration choices. The same configuration practices administrators would use with WebLogic can be followed — configuring services based on provided documentation. But it is also possible for the development team to include these deployable XML artifacts with their application or even bundle them in the same folder or archive. This second model leads to a self-contained application that includes its own configuration dependencies. The Migration Analysis Tool (MAT) provided by JBoss can automatically inspect your WebLogic environment and provide an inventory report of the configured services. Generated reports in HTML format help the architecture team map out service requirements and dependencies.