Stardust executes within a variety of run-time environments. Based on the level of redundancy, availability, throughput and application management, an appropriate deployment option is available for your production environment. Stardust can be deployed in a Web server/servlet container or a fully compliant J2EE application server container. Each option offers strengths and weaknesses over the other options.
Full J2EE implementations of Stardust utilize JMS queues and EJB Session and Message Driven Beans and therefore provide more control, management and scalability of the deployed system. Stardust deployments residing on Web server/servlet containers offer a more light weight, low cost solution, while offering the same functional capabilities as the J2EE deployment. Web server/servlet container deployments do not offer the same level of tuning and performance management as J2EE based deployments but are viable production environments.
The following pages guide you through the setup and deployment of the Stardust Portal and the Process Engine within the supported application servers.
Stardust requires XA-compliant datasources for the JDBC, JCR and JMS connections.
To enable JCR security on an application server deployment which Jackrabbit standalone configuration, the jcr-vfs-2.4.0.jar residing in the WEB-INF/lib folder of your portal WAR file needs to be split into two jar files, one containing factories with spring dependency and one containing the remaining classes.
Extract the following files from jcr-vfs-2.4.0.jar and move them to a new jar named jcr-vfs-factory-2.4.0.jar:
Please make sure these classes are deleted from the original jar and only appear in the new jcr-vfs-factory-2.4.0.jar.
The new jcr-vfs-factory-2.4.0.jar now contains all factories which have a dependency to Spring and can be deployed in the Web application. jcr-vfs-2.4.0.jar now does not have any classes with Spring dependency and can not be added to the Jackrabbit standalone RAR deployment.
Note that in case you are in an EJB deployment the MANIFEST.MF files in your ipp-portal.war and carnot-engine.jar files have to be adapted from jcr-vfs-2.4.0.jar to jcr-vfs-factory-2.4.0.jar.