In addition to the requirements for Deployit, the WLS Plugin has the following additional requirements:
- the user account used to access the WLS server must have permission to perform the following actions:
- run the WLS, wlst.sh script (or wlst.bat on Windows)
The target middleware needs to be set up so that the administrative interfaces of the target middleware can be accessed by running it on the machine on which the administrative server of the software is installed. Deployit does not support a setup in which the administrative client is installed on a different machine.
For WebLogic Server this means that Deployit will use SSH to log in to the machine on which the "admin server" is running, upload any Python files and other files needed to a temporary directory and then invoke the wlst.sh command. Afterwards any temporary files will be removed.
The WLS Plugin defines configuration items (CIs) needed to deploy to Oracle Weblogic middleware. To get more information about these CIs, use Deployit's command line interface (CLI). See the Deployit Command Line Interface (CLI) Manual for more information.
An Apache 2 web server.
Type: com.xebialabs.deployit.plugin.apache.httpd.ci.ApacheHttpdServer
Properties:
- accessLogLocation(STRING): Location where deployit will create a directory where access log will be placed.
- apachectlPath(STRING): Path of the executable that will restart apache, e.g. /usr/sbin/apachectl
- configurationLocation(STRING): Location where deployit will generate apache httpd.conf fragment files.
- errorLogLocation(STRING): Location where deployit will create a directory where error log will be placed.
- host(com.xebialabs.deployit.ci.Host): Host on which the web server runs
- htdocsLocation(STRING): Location where deployit will create a directory (based on the vhost name) where static content will be placed.
- modules(Set<com.xebialabs.deployit.plugin.apache.httpd.ci.ApacheModule>): Modules
An abstraction of Apache Weblogic Plugin Configuration. It is used to generate the configuration file which is included in the Apache main httpd.conf file
Type: com.xebialabs.deployit.plugin.wls.ci.ApacheHttpdWlsPluginConfiguration
Properties:
- name(STRING): Name
- errorPage(STRING): Error Page
- mimeMatchExpressions(STRING): Comma separated list of match expression to proxy requests by MIME type
- pathExpressions(STRING): Comma separated list of path to be used for proxing requests by path
Description unavailable
Type: com.xebialabs.deployit.plugin.wls.ci.ApacheHttpdWlsPluginConfigurationMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- clusters(Set<com.xebialabs.deployit.plugin.wls.ci.WlsCluster>): Clusters
- sourcePropertyOverrides(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Overrides for properties of the mapping's source. The key is the property name (consult the documentation or run 'describe' in the CLI), the value is the value to set. Only string, integer and enumerable properties can be overridden. Example: Key: redeliveryLimits, Value: 2
- virtualHost(STRING): Virtual Host
An generic Apache 2 module.
Type: com.xebialabs.deployit.plugin.apache.httpd.ci.ApacheModule
Properties:
- moduleName(STRING): the module name, eg jk_module
- modulePath(STRING): Path to modjk module eg libexec/mod_jk.so
A WebLogic Cluster, a member of WebLogic Domain. It can have WebLogicServers as it's members
Type: com.xebialabs.deployit.plugin.wls.ci.WlsCluster
Properties:
- domain(com.xebialabs.deployit.plugin.wls.ci.WlsDomain): The domain to which the WebLogic Cluster belongs
- name(STRING): Name of the WebLogic Cluster
- servers(Set<com.xebialabs.deployit.plugin.wls.ci.WlsServer>): Servers in the WebLogic Cluster
A mapping of a WebLogic resource for a WlsCluster to a WlsCluster
Type: com.xebialabs.deployit.plugin.wls.ci.WlsClusterResourceMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- sourcePropertyOverrides(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Overrides for properties of the mapping's source. The key is the property name (consult the documentation or run 'describe' in the CLI), the value is the value to set. Only string, integer and enumerable properties can be overridden. Example: Key: redeliveryLimits, Value: 2
A datasource to connect to a database.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsDataSource
Properties:
- driver(STRING): The driver of the datasource, the classname, e.g. oracle.jdbc.xa.client.OracleXADataSource
- init(INTEGER): The initial connectionpool size.
- jndiName(STRING): The JNDI name of the datasource, e.g. jdbc/orderdb
- max(INTEGER): The maximum connectionpool size.
- name(STRING): The name of the datasource in the WebLogic configuration, e.g. Order DataSource
- uri(STRING): The JDBC uri to the database, e.g. jdbc:oracle:thin:@ora-prod:1521:orders
- password(STRING): The password credential for the database, e.g. tiger
- properties(STRING): A comma separated list of name=value pairs.
- userName(STRING): The username credential for the database, e.g. scott
A mapping of a datasource to a WLS domain with specified targets
Type: com.xebialabs.deployit.plugin.wls.ci.WlsDatasourceToDomainMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- sourcePropertyOverrides(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Overrides for properties of the mapping's source. The key is the property name (consult the documentation or run 'describe' in the CLI), the value is the value to set. Only string, integer and enumerable properties can be overridden. Example: Key: redeliveryLimits, Value: 2
- targets(Set<com.xebialabs.deployit.plugin.wls.ci.WlsTarget>): The targets (WlsCluster, WlsServer), where the datasource is mapped to
Deployable Oracle Service bus Custumization File artifact.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsDeploymentPlan
Properties:
- location(STRING): Location of the artifact.
- name(STRING): The technical name of the artifact as it will be used within application servers.
A WebLogic Domain.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsDomain
Properties:
- activeHost(com.xebialabs.deployit.ci.Host): The host that runs the admin server
- adminServerName(STRING): The name of the admin server
- name(STRING): Name of the WebLogic Domain
- password(STRING): Password which is used to login to the WebLogic Domain.
- port(INTEGER): Port to be used by the AdminServer for this domain
- startMode(ENUM): Tells how a managed server is start and stop, default is NodeManager, others are Script or Windows Service
- Values: [NodeManager, Script, WindowsService]
- username(STRING): Username which is used to login to the WebLogic Domain.
- wlHome(STRING): The location of the WebLogic Server installation
- domainHome(STRING): The location of the WebLogic domain. Defaults to '/../user_projects/domains/'
- enableWlstShWorkaround(BOOLEAN): Enable workaround for broken wlst.sh script found in some versions of WLS
- wlsVersion(ENUM): Wls Version
- Values: [WEBLOGIC_8, WEBLOGIC_9, WEBLOGIC_10, WEBLOGIC_11]
A mapping of an EAR to a WebLogic target
Type: com.xebialabs.deployit.plugin.wls.ci.WlsEarMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- deploymentPlan(com.xebialabs.deployit.plugin.wls.ci.WlsDeploymentPlan): Deployment Plan
- deploymentPlanStagingDirectory(STRING): Deployment Plan Staging Directory
- deploymentStrategy(ENUM): Deployment Strategy
- Values: [CLASSIC, STOP_START, SIDE_BY_SIDE]
- keyValuePairs(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Key Value Pairs
- placeholderFormat(ENUM): Placeholder Format
- Values: [SPRING, WINDOWS_SHELL, STARS, NONE]
- stageMode(ENUM): Deployment staging mode (default is stage)
- stagingDirectory(STRING): Remote directory where the archives (ear,jar,war) are copied before deploying
- virtualHost(STRING): Virtual Host
A mapping of an EjbJar to a WebLogic target
Type: com.xebialabs.deployit.plugin.wls.ci.WlsEjbJarMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- deploymentPlan(com.xebialabs.deployit.plugin.wls.ci.WlsDeploymentPlan): Deployment Plan
- deploymentPlanStagingDirectory(STRING): Deployment Plan Staging Directory
- deploymentStrategy(ENUM): Deployment Strategy
- Values: [CLASSIC, STOP_START, SIDE_BY_SIDE]
- keyValuePairs(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Key Value Pairs
- mdbListenerPortJndiNameBindings(List<com.xebialabs.deployit.ci.mapping.MdbListenerPortBinding>): Bindings of message driven beans JNDI names to the corresponding listener ports present on the target middleware
- placeholderFormat(ENUM): Placeholder Format
- Values: [SPRING, WINDOWS_SHELL, STARS, NONE]
- stageMode(ENUM): Deployment staging mode (default is stage)
- stagingDirectory(STRING): Remote directory where the archives (ear,jar,war) are copied before deploying
Foreign connection factory represents a connection factory that resides on another server, and which is accessible via JNDI.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsForeignJmsConnectionFactory
Properties:
- foreignJmsServer(com.xebialabs.deployit.plugin.wls.ci.WlsForeignJmsServer): The foreign server in which the foreign connection factory is included.
- localJndiName(STRING): The name that the remote object will be bound to in the local server's JNDI tree.
- name(STRING): The name of the foreign connection factory.
- remoteJndiName(STRING): The name of the remote object that will be looked up in the remote JNDI directory.
A foreign destination (topic or queue) is a destination on a remote server. When this destination is looked up on the local server, a look-up will be performed automatically on the remote JNDI directory, and the object will be returned from that directory
Type: com.xebialabs.deployit.plugin.wls.ci.WlsForeignJmsDestination
Properties:
- foreignJmsServer(com.xebialabs.deployit.plugin.wls.ci.WlsForeignJmsServer): The name of the Foreign JMS Server
- localJndiName(STRING): The name that the remote object will be bound to in the local server's JNDI tree
- name(STRING): The name of this foreign destination
- remoteJndiName(STRING): The name of the remote object that will be looked up in the remote JNDI directory
A WebLogic foreign server representing a JNDI provider that resides outside a WebLogic Server.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsForeignJmsServer
Properties:
- connectionURL(STRING): The URL that WebLogic Server will use to contact the JNDI provider
- initContextFactory(STRING): The initial context of the foreign connection
- name(STRING): The name of the foreign server
A WebLogic JMS Connection Factory
Type: com.xebialabs.deployit.plugin.wls.ci.WlsJmsConnectionFactory
Properties:
- jndiName(STRING): Jndi Name
- name(STRING): The name of the connection factory.
A WebLogic JMS Queue
Type: com.xebialabs.deployit.plugin.wls.ci.WlsJmsDistributedQueue
Properties:
- jndiName(STRING): Jndi Name
- name(STRING): The name of the distributed queue
- forwardDelay(INTEGER): Defaults to -1
- loadBalancingPolicy(ENUM): Load Balancing Policy
- Values: [ROUND_ROBIN, RANDOM]
- members(Set<com.xebialabs.deployit.plugin.wls.ci.WlsJmsQueue>): Members
A WebLogic JMS Queue
Type: com.xebialabs.deployit.plugin.wls.ci.WlsJmsQueue
Properties:
- expirationPolicy(ENUM): The message Expiration Policy to use when an expired message is encountered on a destination
- Values: [DISCARD, LOG, REDIRECT]
- jndiName(STRING): Jndi Name
- name(STRING): The name of the queue
- errorQueue(com.xebialabs.deployit.plugin.wls.ci.WlsJmsQueue): The name of the target error destination for messages that have expired or reached their redelivery limit
- expirationLoggingFormat(STRING): The policy that defines what information about the message is logged when the Expiration Policy is set to Log
- jmsServer(com.xebialabs.deployit.plugin.wls.ci.WlsJmsServer): Jms Server
- redeliveryDelayOverride(INTEGER): The delay, in milliseconds, before rolled back or recovered messages are redelivered, regardless of the RedeliveryDelay specified by the consumer and/or connection factory
- redeliveryLimits(INTEGER): The number of redelivery attempts a message can make before it is moved to the error destination
WebLogic JMSServer that can run on a WebLogic Server.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsJmsServer
Properties:
- fileStorePath(STRING): Path to the file store that the JMSServer will use to store JMS messages. e.g. /var/jms/store1
- name(STRING): Name of the JMSServer. e.g. JMSServer1
A WebLogic Mail Session that facilitates the use of the JavaMail API
Type: com.xebialabs.deployit.plugin.wls.ci.WlsMailSession
Properties:
- jndiName(STRING): Jndi Name
- name(STRING): Name of the Mail Session
- javaMailProperties(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): The JavaMail properties to be set for this Mail Session, as key/value pairs
Work Manager that defines a set of request classes and thread constraints that manage work performed by WebLogic Server instances.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsMaximumThreadsConstraint
Properties:
- name(STRING): Name of the Work Manager
- threadCount(INTEGER): Thread Count
- notes(STRING): Notes
A standard Weblogic Server
Type: com.xebialabs.deployit.plugin.wls.ci.WlsServer
Properties:
- domain(com.xebialabs.deployit.plugin.wls.ci.WlsDomain): WebLogic Domain to which this server belongs
- host(com.xebialabs.deployit.ci.Host): Host on which this server is running
- name(STRING): Name of the WebLogic Server
- port(INTEGER): Port for the WebLogic Server
- arguments(STRING): The arguments for this server, including initial heapsize (e.g. -Xms64m), maxheap size (-Xms256m), and bootclasspath (-Xbootclasspath/p:/var/lib/addons.jar)
- classpath(STRING): Classpath entries for this server.
- enableJVMLogRedirection(BOOLEAN): Enable JVM StdOut to Server Log file
- logFileLocation(STRING): Absolute path of log file. Example; /opt/bea/user_projects/domain/managedserver1/ms1.log
- stageMode(ENUM): Deployment staging mode (default is stage)
- startCommand(STRING): Command that should be executed to start the managed server.
- stopCommand(STRING): Command that should be executed to stop the managed server.
Modification of a WebLogic server
Type: com.xebialabs.deployit.plugin.wls.ci.WlsServerConfigurationModification
Properties:
- classpathAddition(STRING): Classpath entries to add.
- name(STRING): Name
A mapping of a WebLogic resource for a WlsServer to a WlsServer
Type: com.xebialabs.deployit.plugin.wls.ci.WlsServerResourceMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- sourcePropertyOverrides(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Overrides for properties of the mapping's source. The key is the property name (consult the documentation or run 'describe' in the CLI), the value is the value to set. Only string, integer and enumerable properties can be overridden. Example: Key: redeliveryLimits, Value: 2
Deployable WebLogic shared library (Ear, War, Jar) artifact. Note the name of the WlsSharedLibrary must be the same as the Extention-Name specified in the MANIFEST.MF of the library.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsSharedLibrary
Properties:
- location(STRING): Location of the artifact.
- name(STRING): The technical name of the artifact as it will be used within application servers.
- sharedLibraryType(ENUM): The type of Weblogic shared library.
A mapping of a weblogic shared library to WebLogic middleware
Type: com.xebialabs.deployit.plugin.wls.ci.WlsSharedLibraryMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- deploymentStrategy(ENUM): Deployment Strategy
- Values: [CLASSIC, STOP_START, SIDE_BY_SIDE]
- keyValuePairs(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Key Value Pairs
- placeholderFormat(ENUM): Placeholder Format
- Values: [SPRING, WINDOWS_SHELL, STARS, NONE]
- stageMode(ENUM): Deployment staging mode (default is stage
- stagingDirectory(STRING): Remote directory where the archives (ear, jar, war) are copied before deploying
A mapping of a WAR to WebLogic middleware
Type: com.xebialabs.deployit.plugin.wls.ci.WlsWarMapping
Properties:
- source(java.io.Serializable): Source
- target(java.io.Serializable): Target
- contextRoot(STRING): Context root to deploy to
- deploymentPlan(com.xebialabs.deployit.plugin.wls.ci.WlsDeploymentPlan): Deployment Plan
- deploymentPlanStagingDirectory(STRING): Deployment Plan Staging Directory
- deploymentStrategy(ENUM): Deployment Strategy
- Values: [CLASSIC, STOP_START, SIDE_BY_SIDE]
- ejbReferences(List<com.xebialabs.deployit.ci.mapping.EjbReference>): Specifies the mapping from ejb reference jndi names and locals used in the web.xml to bean jndi names available in middleware
- keyValuePairs(List<com.xebialabs.deployit.ci.mapping.KeyValuePair>): Key Value Pairs
- placeholderFormat(ENUM): Placeholder Format
- Values: [SPRING, WINDOWS_SHELL, STARS, NONE]
- resourceEnvironmentEntryReferences(List<com.xebialabs.deployit.ci.mapping.ResourceReference>): Specifies the mapping from resource environment references jndi names and types used in the web.xml to resource references jndi names available in middleware
- resourceReferences(List<com.xebialabs.deployit.ci.mapping.ResourceReference>): Specifies the mapping from resource references jndi names and types used in the web.xml to resource references jndi names available in middleware
- stageMode(ENUM): Deployment staging mode (default is stage
- stagingDirectory(STRING): Remote directory where the archives (ear, jar, war) are copied before deploying
- virtualHost(STRING): Virtual host to deploy to
Work Manager that defines a set of request classes and thread constraints that manage work performed by WebLogic Server instances.
Type: com.xebialabs.deployit.plugin.wls.ci.WlsWorkManager
Properties:
- name(STRING): Name of the Work Manager
- maximumThreadsConstraint(com.xebialabs.deployit.plugin.wls.ci.WlsMaximumThreadsConstraint): Maximum Threads Constraint
