Jump to: navigation, search

Difference between revisions of "Stardust/Knowledge Base/Getting Started/RTE on AWS"

(Troubleshooting)
(Other Troubleshooting)
Line 77: Line 77:
 
''This problem will be addressed soon on the original image.''
 
''This problem will be addressed soon on the original image.''
  
==Other Troubleshooting==
+
==Brute Force Troubleshooting==
 
If something totally unexpected happens in the Portal, try a reboot of your EC2 instance after making sure that no other user is working on the system.
 
If something totally unexpected happens in the Portal, try a reboot of your EC2 instance after making sure that no other user is working on the system.

Revision as of 10:27, 9 October 2013

Set Up

To create a full Stardust Runtime Environment on Amazon Web Services EC2 Infrastructure,

ProductPage.gif

You will be asked to login with an existing Amazon account or to register for one:

AmazonLogin.gif

Launch with one 1-Click will launch the Stardust Runtime on your EC2 Instance Type of choice:

InstanceTypes.gif

The AWS Virtual Machine Image (AMI) is configured to run on all Instance Types including the Standard Micro (t1.micro) type and your choice depends entirely on the expected load profile. For first experiments the Standard Micro is sufficient.

Please consider that although there are no charges for Stardust, Amazon charges you for most of the EC2 configurations.

Select your data center region of choice - the Stardust AMI is available for all AWS data center regions:

Region.gif

You will be prompted to confirm that you do not want to create a Key Pair:

KeyPair.gif

You need a Key Pair this if you intend to login to operating system of the EC2 instance via Secure Shell (SSH) and modify the setup there, e.g. for

  • troubleshooting (see below),
  • tuning for larger deployments or
  • adding application specific Java byte code.

Hence, we recommend to generate Key Pair and and use it.

If you just intend to run and configure Stardust via the Stardust Web Portal, there is no need to create a Key Pair and you can consider the installation a block box.

Login

After you have launched your instance and the instance is available, lookup the Public DNS Name for the instance and login via

http://<Public DNS Name>:8080/stardust-standard

and

  • User: motu
  • Password: motu

This is the Stardust root user. Make sure that you can change the password later.

After successful login you can use the Stardust Portal.

Process Model Creation and Deployment

If you are keen to start playing and do not bother to create your own Process Model at this point, pick one of the sample process models from Git e.g. the Car Rental Example (right-click the link before and save the file) and just upload and deploy under Administration > Model Management (more details here).

Model-deployment.gif

If you intend to create your own Process Models, you can either use the Browser Modeler which is immediately available in the Stardust Portal of your Amazon EC2 Instance or use the Stardust Eclipse Modeler - which requires you to download Eclipse and install Stardust.

User Creation and Role Assignment

Do not forget to create users and assign to roles so that you can start processes and perform activities in your process.

Troubleshooting

Below a few things which might help you if you are facing problems. If nothing helps, search and/or post in the Stardust Forum. You will very likely find help there.

Tomcat Out of Memory Issue

Currently, the Tomcat installation on the Stardust Image is not configured with the appropriate memory size for its Java VM. To address this issue, login to your EC2 Instance using your Key Pair and add the following

set CATALINA_OPTS=%CATALINA_OPTS% -Dtrue=true -Xms1200m -Xmx1200m -XX:NewSize=300m -XX:MaxNewSize=300m -XX:PermSize=256m -XX:+UseTLAB

at the beginning of /home/ec2-user/apache-tomcat-6.0.32/bin/catalina.sh.

This problem will be addressed soon on the original image.

Brute Force Troubleshooting

If something totally unexpected happens in the Portal, try a reboot of your EC2 instance after making sure that no other user is working on the system.