Directory structure

Aura is, at its core, a deployment and configuration automation engine with currect support for WebSphere. The concept is to define the configuration as code in XML and version control it with application code. Throughout that Resource xml are tokenised thus can be applied to any environment.

Aura Working directory: This is structure in your source code tree, Run aura commands from cn

├── PetClinic
|   ├── pom.xml
|   ├── aura.xml
|   ├── src
.
.
├── _config
|   ├── resources
|   |	├── ..Resource.xml
|   |	├── ..Resource.xml
|   ├── properties
|   |	├── [env.name].properties
|   ├── ear
|   |	├── PetClinic.ear
|   |	├── ...ear
|   ├──	├── DeployData
|   |	|   ├── PetClinic-deploydata.xml
└── └── └── └── ..-deploydata.xml

An overview of what each of these does:

File / Directory	Description
`aura.xml`	Optional file to specify the location directoies.
`resources`	Location for all the resource xml files for the application
`properties`	Location for values of token for all the environments
`ear`	EAR files and deploydata files for the application

A basic Aura install looks like this

├── bin
├── lib
├── opt
|   ├── ant-contrib
|   ├── apache-ant-1.7.1
|   └── groovy-1.7.4
├── properties
├── resource
|   ├── extractTemplates
|   	├── cell
|   	├── cluster
|   	├── node
|   	└── server
├── _var
|   ├── common
|   └── scripts
└── └── was

An overview of what each of these does:

File / Directory	Description
`bin`	Aura bat/shell scripts.
`lib`	aura and supporting lib jars,
`opt`	Thirparty tools like ant-contrib, ant and groovy.
`properties`	properties required for core aura, e.g. log4j, commons-logging etc
`resources`	This is location for templates Resource xml for extract operation.
`var`	Directory contains groovy, ant etc scripts required.

Aura Repo structure looks like. Aura keeps extracted config, reports, plugins in Aura_Repo

├── _plugins
|   ├── was-remote
|   |	├── etc
|   |	├── properties
|   |	└── lib
|   ├── resources
|   |	├── config
|   |	└── report
|   |	└── ear
└── └── environments

An overview of what each of these does:

File / Directory	Description
`plugins`	Location where plugins will be installed.
`resources`	Location where the outputs like ResourceXML, HTML reports and ear are exported
`environments`	Environment connection details are stored in this location

Back