Expanding in the Prime Radiant
On the expansion page, it is possible to expand, build and deploy applications.
You can select an applicationInstance in the table on the left to open a detailed view.
new instance button if you want to create a new ApplicationInstance.
The first tab
Expansion will show some info on your ApplicationInstance. For a new ApplicationInstance, only the export button will be enabled, alongside the buttons to view, edit and delete it.
export button will export the application and related components, settings and expansion-settings to the directory linked to the
custom base of the ApplicationInstance.
If we wish to expand this application, we will need to first generate a new expansionSettings. To do this, click on the
generate expansionSettings button. This will enable the other buttons:
The Prime Radiant will automatically add
nsx-default-stack to the expansion-resources.
This will add the base-components, web-styles, expanders etc. to your expansion. (See more)
With the expansionSettings configured, you can now expand and build your application.
exportbutton before expanding.
Adding new expansion-resources
You can add other expansion-resources by inserting it in the input field below.
If the expansion-resource does not appear it the dropdown, you can press
enter and it will prompt to add it to the database.
When added, the expansion-resource will be included the next time you press
The overlay button will look for any overlay script in the source-base and execute it.
The expand button also allows some alternative modes:
- Clean Expand: Removes the expansion directory before expanding. This makes sure nothing remains in the directory that is not expanded or harvested. This may be useful to clean deleted ext files or artifacts generated for a deleted element.
- Skip Overlay: Expand the application, but skip the overlay phase. This generates the application as if there were no overlays, so you can compare the result with the overlays you have.
Similarly, the build button also allow you to perform a Clean build, which will execute
mvn clean package.
The Prime Radiant has built in functionality to deploy your application locally in order to review and test it.
Select the application instance you want to deploy and go to the
Here you can press
request deploy to create a new ApplicationDeployment instance.
Next, edit the instance and set the deploy-base. By default, there are a number of deploy-bases for each application server type. It’s best to use a deploy-base with only one application.
Once the deploy-base is set, the deploy actions are enabled. For the first deployment, it’s best to execute them in order.
- Generate Deploy Configuration: Generate config files that are specific to your application. This includes, among other, the data-sources for each component.
- Prepare: Clean the deploy-base and copy the configuration files from the previous step to the deploy-base.
- Do Start/Stop: Start or stop the application
Once configured the application can be started and stopped without having to reconfigure. However, when you add a new component to your application, you should repeat the first two steps to make sure the configuration is correct.
If the application is live, you can open the login page by following the link in the table.