Changes Required When the JMS Provider is Upgraded to WebLogic Server
7.1.1 Configuring Web Sites and AJP Connections in Oracle WebLogic Server
OC4J provided users with the ability to define multiple Web sites for each OC4J instance. In other words, you could define a unique listener, with its own port and protocol. Each Web application deployed to the OC4J instance could be bound to a specific OC4J web site, which directed any requests to that specific port and protocol to the desired application.Parts
» Oracle Fusion Middleware Online Documentation Library
» OC4J and Oracle WebLogic Server Clustering Features
» Comparing OC4J and Oracle WebLogic Server Directory Structures
» Basic Content and Organization of a Domain
» A WebLogic Server Installation Can be Used to Configure Multiple Domains As
» A WebLogic Server Instance Is Always Associated With a Single Java Virtual Machine
» A WebLogic Server Instance Processes All Application Requests on the Same Port by
» A WebLogic Server Instance Is Always Configured With an HTTP Listener and Does Not
» Oracle WebLogic Server Installation and Configuration Tools for OC4J Users
» Comparison of OC4J and Oracle WebLogic Server Administration Tools
» Starting and Stopping Servers
» Performing Diagnostics on a Domain
» Standards Support for OC4J and Oracle WebLogic Server
» Task 1: Verify that Your Application Deploys and Works Successfully on OC4J
» General Guidelines for Selecting Your Development Tools
» Using the SmartUpgrade Oracle JDeveloper Extension and Command-Line Tool
» Task 3: Verify That Your Application Supports Java Development Kit JDK 6
» Comparison of OC4J and Oracle WebLogic Server Deployment Descriptors
» Guidelines and Resources for Upgrading Deployment Descriptors for Oracle WebLogic Server
» About Security Elements in Deployment Descriptor Files
» Upgrading Deployment Plans Task 4: Upgrade the Application Deployment Descriptors
» APIs Available With the Java Required Files JRF Domain Template
» Other Oracle WebLogic Server API Requirements
» General Guidelines for Upgrading to Oracle WebLogic Server JAX-RPC and JAX-WS Web Services
» Differences Between a Development Environment and a Test or Production Environment
» Selecting an Oracle Fusion Middleware Software Suite
» Creating a New Domain With the JRF Template
» Extending an Existing Domain With the JRF Template
» Task 2: Verify the New Oracle Fusion Middleware 11g Environment
» General Information About Defining Data Sources for OC4J and Oracle WebLogic Server
» Upgrading Application-Level OC4J Data Sources
» Upgrading Instance and Group-Level OC4J Data Sources
» JDBC Connection Pools and Managed Data Sources in OC4J and Oracle WebLogic Server
» Overview of JMS Support in OC4J and Oracle WebLogic Server
» Creating and Managing JMS Resources in OC4J and Oracle WebLogic Server
» Configuring OC4J Remote JMS Resources on Oracle WebLogic Server
» Using Shared Libraries and Class Loading on Oracle WebLogic Server
» Configuring Startup and Shutdown Classes
» Configuring Security on Oracle WebLogic Server
» Configuring Logging on Oracle WebLogic Server
» Task 4: Redeploy the Application on Oracle WebLogic Server
» Task 5: Verify the Redeployed Applications
» Impact of Upgrade on Java Server Pages and Servlet Clients
» Changes Required When the JMS Provider is Upgraded to WebLogic Server
» Changes Required When the JMS Provider Remains in OC4J
» Configuring Web Sites and AJP Connections in Oracle WebLogic Server
» How Oracle HTTP Server Is Configured for OC4J
» How Oracle HTTP Server is Configured for Oracle WebLogic Server
» Deciding Upon a Location for Your Web Tier Components
» Task 3a: Start the Upgrade Assistant for an Web Tier Upgrade
» Upgrading the Web Tier Components
Show more