An Oracle blog about Middlware
- April 26, 2014
ADF Deployment Options (2)
Deployment with JDeveloper IDE
Interface
- This is the basic deployment mechanism every developer is taught to use via the IDE Application menu "Deploy" option
Manual/Automated
- Within the IDE, the developer can kick this off manually, there is no automated option.
Start from source code or JAR/EAR
- It requires to build the JAR/EAR from the source code, so the source code must be checked out first.
Suitable for development server
- This requires the developer to know the WLS admin account name and password.
Suitable for test/production servers
- But it is not appropriate they know it for your test/QA/production servers
Apply WLS deployment plans
- WLS deployment plan must be manually created but can be applied at deployment time
Apply ADF/MBean runtime changes
- There is no mechanism to change the ADF application at runtime via the MBean interface
Supports WLS production redeployment
- And there is no support for WLS "production redeployment"
How To?
Deployment Options table
| Deployment Options | JDeveloper | WLS console | FMW console | weblogic.Deployer | WLST |
| Interface | IDE | Web | Web | Command line, OS scripts or Ant | Command line, OS scripts or Ant |
| Manual/Automated | Manual | Manual | Manual | Both | Both |
| Start from source code or JAR/EAR | Source | JAR/EAR | JAR/EAR | JAR/EAR | JAR/EAR |
| Suitable for development server | Yes | Yes | Yes | Yes | Yes |
| Suitable for test/production servers | Yes | Yes | Yes | Yes | |
| Apply WLS deployment plans | Yes | Yes | Yes | Yes | Yes |
| Apply ADF/MBean runCme changes | Yes | Yes | |||
| Supports WLS producCon redeployment | Yes | Yes | Yes |
Be the first to comment
Comments ( 0 )