Deploying Applications

Stardust provides preconfigured deployment configurations as Maven archetype templates for specific application server. You can download them from the Stardust artifactory matching your requirements.

Refer to chapter Creating a Stardust Runtime Environment with Apache Maven in the Stardust Installation Guide for details.

Stardust provides predefined deployment configurations to prepare an EAR or WAR deployment for specific application servers. Please refer to our Stardust Knowledge Base for details on the currently provided archetypes and how to retrieve them.

Configuring Deployment Properties

Supplement your ipp-portal.war with a valid carnot.properties file.

Create a new directory, for example stardustPortal, where you unpack the provided ipp-portal.war file:
```
jar -xvf ipp-portal.war.
```
Place your valid carnot.properties file in the WEB-INF/classes subdirectory.
In case your database is configured to have AutoCommit set to true, add the AuditTrail.FixAutoCommit property in the carnot.properties file and set it to true to enable commit control by the engine:
```
AuditTrail.FixAutoCommit = true
```
Additionally add the AuditTrail.Type property:
```
AuditTrail.Type = <database type>
```
Please refer to the chapter Client Side Properties in the Developers Handbook for detailed information on these properties.
Jar this directory structure back in the deploy directory by using the command:
```
jar cvf ipp-portal.war *
```

Configuring Credentials for the Technical User

A default technical user exists with the credentials motu/motu in the realm carnot. To configure credentials for a technical user, properties are provided, which you can set in your client-side carnot.properties file. The following table provides an overview on these properties.

Description	Default	Overwrite with client side property
Account	motu	Security.ResetPassword.TechnicalUser.Account
Password	motu	Security.ResetPassword.TechnicalUser.Password
Realm	carnot	Security.ResetPassword.TechnicalUser.Realm
Partition	Note that the partition provided by the user who requests the new password is used!

Please note that a technical user has to be created manually for each partition. Technical users do not have to be administrators.

Deploying Custom Applications

The ipp-portal.war created in this way now has to be deployed to your application server.

Deploy the resulting WAR file with the deployment mechanisms of your application server. For example if you deploy to Apache Tomcat, copy the ipp-portal.war to the webapps folder of your Tomcat installation and restart the server.

To prepare the deployment please differ between applications to be used by the engine and interactive applications. Please refer to the chapter Deploying Stardust Components to a Web Application Server for detailed information, e.g. on how to enable the usage of a ContextClassLoader.

Interactive Applications

To deploy your custom interactive applications, like JSF applications or backing beans, you have to add them to your WAR file as described above.

Non-Interactive Applications

Custom non-interactive application classes needed by the engine, like EJBs, must be available in the engine context and have to be added to your EAR file. This process is described in detail in the chapter Deploying Stardust Components to an EJB Application Server.

The classes used in the WAR-context must be packaged in a JAR inside the WAR file, whereby classes used in the WAR and EAR must be packaged in a JAR inside the EAR file.