What is configured when you create or augment a profile

When you create a WSRR profile, or augment an existing profile to include WSRR, you add components and perform configurations in addition to those included in a standard WebSphere Application Server profile.

WSRR profile creation or augmentation for a stand-alone server creates and configures the following components.

• Creates and configures a JDBC provider and data sources for all the database tables. Three data sources are created along with three JAAS aliases.
• Creates and partially configures a Mail provider and session. (If you want to use e-mail notification in WSRR, you must complete the configuration, see Subscription notifier.)
• Creates, configures and starts a messaging engine.
• Creates and configures a scheduler and a work manager.
• If specified, creates and configures security settings and auth aliases.
• Configures transaction and SOAP timeout settings to the WSRR recommended values (see the Preventing time outs for more details)
• Creates a Service Integration Bus, topic spaces, topics, queues, connection factories and a JMS alias.
• Deploys the service registry EAR.
• Deploys the WSRR report viewer EAR.
• Deploys the WSRRCRE EAR.
• Configures settings in the JVM.

When you create and augment a Deployment Manager profile, or augment an existing Deployment Manager profile to include WSRR, much of the creation and configuration of components is performed afterwards. Augmentation installs a WebSphere Application Server Administrative Console plug in, you then use the Deployment Manager administrative console to create, configure, and deploy WSRR components to cluster members or federated servers.