Successful but tricky installation on AWS EC2

raphael

<p>Hello,</p>
<p> </p>
<p>For those who like to test iHub on Linux, after several trials and errors, this procedure works using Amazon Web Services:</p>
<p> </p>
<p>Create an EC2 m3.large with for this official AMI below and an 8 Gb SSD EBS attached as the root partition:</p>
<p><a>CentOS-6.5-GA-03.3-f4325b48-37b0-405a-9847-236c64622e3e-ami-6be4dc02.2 (ami-42718735)</a></p>
<p> </p>
<p>After the EC2 initialization process, this security inbound rules have been defined as:</p>
<p> </p>
<div>
<div>
<div>All ICMP</div>
</div>
</div>
<div>
<div>
<div>All</div>
</div>
</div>
<div>
<div>
<div>N/A</div>
</div>
</div>
<div>
<div>
<div>0.0.0.0/0</div>
</div>
</div>
<div>
<div>
<div>All TCP</div>
</div>
</div>
<div>
<div>
<div>TCP</div>
</div>
</div>
<div>
<div>
<div>0 - 65535</div>
</div>
</div>
<div>
<div>
<div>****.****.****.****/32</div>
</div>
</div>
<div>
<div>
<div>SSH</div>
</div>
</div>
<div>
<div>
<div>TCP</div>
</div>
</div>
<div>
<div>
<div>22</div>
</div>
</div>
<div>
<div>
<div>****.****.****.****/32</div>
</div>
</div>
<div>
<div>
<div>Custom TCP Rule</div>
</div>
</div>
<div>
<div>
<div>TCP</div>
</div>
</div>
<div>
<div>
<div>8700</div>
</div>
</div>
<div>
<div>
<div>****.****.****.****/32</div>
</div>
</div>
<p> </p>
<p> </p>
<p>****.****.****.**** stands for a WAN IP address.</p>
<p> </p>
<p>All TCP rule is overkilled but used just during the installation.</p>
<p> </p>
<p>Also this EC2 instance has to be associated with an Elastic IP and its corresponding DNS entry in Route 53.</p>
<p> </p>
<p>Through SSH, an "ftype" user has been created, the ActuateBIRTiHubFType.tar.gz has been uploaded and unarchived.</p>
<p> </p>
<p>The default internal firewall must be altered as this:</p>
<p>:INPUT ACCEPT [0:0]<br>
:FORWARD ACCEPT [0:0]<br>
:OUTPUT ACCEPT [123:20256]<br>
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT<br>
-A INPUT -p icmp -j ACCEPT<br>
-A INPUT -i lo -j ACCEPT<br>
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT<br>
-A INPUT -p tcp -m tcp --dport 8700 -j ACCEPT<br>
-A INPUT -j REJECT --reject-with icmp-host-prohibited<br>
-A FORWARD -j REJECT --reject-with icmp-host-prohibited<br>
COMMIT<br>
# Completed on Tue Oct 28 14</p>
<p> </p>
<p>From this point, I have followed the Actuate "quick-start-install-ftype-linux.pdf".</p>
<p> </p>
<p>The installation run smoothly but the launching failed.</p>
<p> </p>
<p>Following the thread below, the installation process was completed:</p>
<p><a data-ipb='nomediaparse' href='http://developer.actuate.com/community/forum/index.php?/topic/35168-errors-activating-on-rh-linux/'>http://developer.actuate.com/community/forum/index.php?/topic/35168-errors-activating-on-rh-linux/</a></p&gt;
<p> </p>
<p>IHub is very sensitive about the hostname.</p>
<p> </p>
<p>After activation, everything seems to work flawlessly.</p>
<p> </p>
<p>Note: I tried also with CENTOS 7 and Ubuntu Server 10.04 LTS without success before.</p>
<p> </p>
<p>Good luck!</p>
<p> </p>
<p>It would be very interesting if Actuate could provide a ready to use iHub F-Type AMI on AWS Marketplace.</p>
<p>It could save a lot of time to every users with an AWS account :P</p>

lvictor

<p>Nice to see you achieved the installation process.</p>
<p> </p>
<p>In my case, on a CentOS 7 virtual machine, installation process seems to work (it says "install suceed") but no process is launched when I start iHub, port 8700 is not open, so I can't access to <a data-ipb='nomediaparse' href='http://domain.local:8700/iportal'>http://domain.local:8700/iportal</a>. </p>
<p> </p>
<p>You said you tried with CentOS 7 "without success before". Did you finally succeed ?</p>