Steps

• wls.EarModule: Ear with values configured for a deployment

• wls.WarModule: War with values configured for a deployment

• wls.EjbJarModule: EJB with values configured for a deployment

• wls.SharedLibraryWarModule: The Java EE library feature provides an easy way to share one or more types of Java EE modules among multiple Enterprise Applications. In particular, a Java EE library is a stand-alone EJB or Web Application module, multiple EJB or Web Application modules packaged in an Enterprise Application (EAR), or a single plain JAR file that is registered with the Java EE application container upon deployment

• wls.SharedLibraryJarModule: The Java EE library feature provides an easy way to share one or more types of Java EE modules among multiple Enterprise Applications. In particular, a Java EE library is a stand-alone EJB or Web Application module, multiple EJB or Web Application modules packaged in an Enterprise Application (EAR), or a single plain JAR file that is registered with the Java EE application container upon deployment

• wls.DataSource: An object bound to the JNDI tree that provides database connectivity through a pool of JDBC connections

• wls.MailSession: Mail sessions facilitate the process of using the JavaMail APIs, which provide applications and other J2EE modules with access to Internet Message Access Protocol (IMAP)- and Simple Mail Transfer Protocol (SMTP)-capable mail servers on your network or the Internet

• wls.PersistentStore: The persistent store supports persistence to a file-based store or to a JDBC-enabled database.

• wls.FilePersistentStore: A file-based persistent store.

• wls.JmsPersistentStore: A persistent store for JMS messages.

• wls.JmsFilePersistentStore: A file-based persistent store for JMS messages.

• wls.JmsJdbcPersistentStore: A database backed persistent store for JMS messages.

• wls.Queue: A JMS Queue Defines a point-to-point destination type, which are used for asynchronous peer communications. A message delivered to a queue is distributed to only one consumer

• wls.Topic: A JMS Topic Defines a topic destination type, which are used for asynchronous peer communications. A message delivered to a queue is distributed to only or many consumers

• wls.UniformDistributedQueue: A distributed Queue defines a set of queues that are distributed on multiple JMS servers, but which are accessible as a single, logical queue to JMS clients

• wls.ConnectionFactory: A connection factory defines a set of connection configuration parameters that are used to create connections for JMS clients. Connection factories can configure properties of the connections returned to the JMS client, and also provide configurable options for default delivery, transaction, and message flow control parameters

• wls.UniformDistributedTopic: A distributed Queue defines a set of topics that are distributed on multiple JMS servers, but which are accessible as a single, logical topic to JMS clients

• wls.DeployedFolder: Deployed configuration Folder

• wls.DeployedFile: Deployed configuration File

• wls.CopiedDeploymentPlan: Deployment plan XML file that is deployed to the WLS AdminServer host