Install WSO2 Stratos 2.0 on single node? - wso2

I have setup WSO2 Stratos 2.0 on single node using following documentation http://docs.wso2.org/display/Stratos200/OpenStack I have downloaded wso2s2-openstack-1.0.1, extract zip file, and follow the instructions in the README.txt file.
But I don't understand this step in Readme.txt file:
Open up the security rules in openstack for the following ports which
are from ./con/setup.conf
22, 443, 8280, 4103, 4100, s2_db_port, agent_https_port, agent_http_port, bam_port, elb_port, agent_clustering_port,
sc_cluster_port, elb_cluster_port,
bam_reciever_port, bam_reciever_secured_port, cassandra_port, userstore_db_port, s2_db_port,
in Openstack install section
Can you give me more detail about this step?
Thank you very much! :)
In fact, I want to build a private cloud on my VM.
In my scenario, I use OpenStack (Havana) as IaaS and WSO2 Stratos 2.0 as PaaS. But I can find any document on infrastructure level about deploy Stratos on IaaS.
WSO2 have document on installing Stratos, but indeed I am very confuse how OpenStack and Stratos combine with each other?
Cloud is very new to me and I am learning.
So, could someone give me the right direction to learning or some useful link for me started.
And another question: install Stratos on OpenStack controller or compute node or both?
I appreciate your help.

If you are installing Stratos on a single node, for prototyping or testing purposes, you probably don't need Openstack in the first place. Any (virtual) machine would do.
If you use Openstack, it happens that all the ports in your virtual instances are closed by default. If you need specific ports to be accessible to that server, you must enable them, creating security rules in the corresponding security group where this machine belongs.
If using nova-network, this would open 8280 in the 'default' group, for any address:
nova secgroup-add-rule default tcp 8280 8280 0.0.0.0/0
See instructions at:
http://docs.openstack.org/network-admin/admin/content/enabling_ping_and_ssh.html

Related

How can I setup Jmeter distributed configuration in cloud(AWS)?

I am currently running JMeter in 5 local VMs in which one acts as master and 4 as slaves. I want to move them to amazon servers. Can anyone suggest step by step configuration methods. Searched internet and couldn't find a documentation with full clarity. Or can anyone share a good documentation link on this?
jmeter version: 3.2
My requirements are:
1 master and 4 slaves.
the master should have Linux GUI because I need JMETER GUI to run the test, since we are analyzing real time running data.
First of all, double check you looked for instructions well enough, i.e. there is JMeter ec2 Script project which automates the process of installation and configuration of JMeter remote engines.
In general, the process doesn't differ from configuring JMeter in distributed mode locally, Amazon EC2 instances are basically the same machines as local ones and require the same configuration steps. Just make sure to open the following ports:
1099
the port you define as server.rmi.localport
the ports you define as client.rmi.localport
It has to be done both in Linux Firewall and AWS Security Groups
Check out the following material:
Remote Testing
JMeter Distributed Testing Step-by-step
JMeter Distributed Testing with Docker
Load Testing with Jmeter and Amazon EC2

Corda apps not visible on 10004 port

I'm working on Corda on Azure Cloud.
I have deployed a Corda blockchain (4 nodes, 1 notary and 1 network manager) in Corda 2.0.
I have tried to follow the tutorial https://docs.corda.net/azure-vm.html.
When I go to http://(public IP address):10004/, I don't see my Cordapps.
I have 2 installed (jar files in /opt/corda/plugins) on each node: corda-finance (already installed by Azure) and yo!app (version M11)
I see :
Installed CorDapps
No installed custom CorDapps.
If I go to http://(public IP address):(port)/web/yo, I have :
Corda O=Organisation 2 (Corda 2.0.0), L=London, C=GB
HTTP ERROR 404
Problem accessing /web/yo. Reason:
Not Found
Powered by Jetty:// 9.4.7.v20170914
Do anyone know why?
I found the problem,
The yo!app version M11 doesn't work for Corda V2. There is nothing in the tutorial saying what to do (I think it is outdated) but I have an updated version of yo!app on https://explore.corda.zone/, you can upload it on your node in the pluging folder with
wget http://ci-artifactory.corda.r3cev.com/artifactory/cordapp-showcase/yo-4.jar
strangely the "corda-finance.jar" file don't seem to work, either the jar file is also outdated or it is not a "real" cordapps and thus , it doesn't appear on the web-service page.
Hope this can be helpful to someone else.

Issue in running corda as Windows service

I am trying to run corda as a Windows service. I followed all the steps in documentation. As per the steps the node configuration and corda.jar is invoked by a NSSM service manager. Nowhere it is mentioned to start the controller node. I assume a controller node should be running as a prerequisite.
In node.conf file
networkMapService {
address="networkmap.foo.bar.com:10002"
legalName="O=FooBar NetworkMap, L=Dublin, C=IE" }
networkMapService is pointing to some address. So should I deploy and run the Cordapp before I run the nssm.bat file ?
However I when I opened the log file I see the below error though I have the certificates in place.
Exception during node startup
java.lang.IllegalArgumentException: Identity certificate not found. Please either copy your existing identity key and certificate from another node,
or if you don't have one yet, fill out the config file and run corda.jar --initial-registration.
I am clueless. Please someone help me understand this process.
There are a few issues with the docs there:
When deploying a node, we are assuming that you are going to provision real certificates to the node. This step is only documented in the Linux instructions (See step 11: 11. Provision the required certificates to your node. Contact the network permissioning service or see Network Permissioning). You can create your own certificates by following the instructions here (https://docs.corda.net/permissioning.html)
We are assuming that there is already a node operating a network map service at the address listed in node.conf
I'll raise a PR to fix these issues.
If you are interested in running nodes across different machines in dev mode instead, see https://docs.corda.net/tutorial-cordapp.html#running-nodes-across-machines.

Installing AD and MSExchange 2016 in AWS EC2

I am trying to install an MSExchange 2016 in an EC2 instance from scratch without success. By from scratch, I mean I start from a new EC2 instance without any AD yet installed.
I am not very familial with Windows Server. I got a lot of problem during the installation. By digging the web, I fixed a lot of them, but I think there is something I miss to succeed in my installation. Any help would be greatly appreciated
Here is the procedure I followed:
I created an EC2 Windows Server 2012RC2 instance
I created a simple Active Directory in AWS.
I provided the AD DNS to my Windows Server (via Network and Sharing Center, properties of Internet Protocol v4)
I joined the server into that AD (Via Control Panel > System and Security > System, change computer workgroup to the domain defined in my AWS Simple AD)
Restart computer
Log into the server as Administrator, with the AD domain
Download Exchange from here
Set-up the active directory, as in this procedure: https://judeperera.wordpress.com/2015/07/24/step-by-step-guide-for-installing-exchange-server-2016-preview/
The Step 4.1. of that procedure indicates to execute the following code
Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
When I execute it, I get the following error:
I do not understand what I need to do/fix to continue the installation.
Thanks in advance for your help!
The issue you are encountering is that Simple Directory is not an Active Directory product, it is powered by Samba v4. What you need is to setup a Microsoft Active Directory (Enterprise Edition) or Microsoft AD, which is powered by Windows Server 2012 R2. The Simple AD is powered by Samba v4 and is simply Active Directory compatible but does not support the added schema features which are needed by Exchange Server 2016.
The other option is to back away from hosting your own instance of Exchange server and instead take a look at AWS WorkMail. It is an exchange like service which supports active sync with Outlook 2007+ and all current mobile smart devices such as Android and iOS. I currently use this and it took a lot of the headache out of managing my own mail server as the complexities are offloaded to the AWS environment and all you need to do it add mail accounts and group addresses.
Either option should solve your issue.

IBM Mobile first testing server using AWS (Amazon Web Service)

2 questions:
1) Do we need to purchase additional license to test mobile first on AWS?
Currently we are using the free eclipse version for the developer to test on their own macbook.
At the moment, we need to setup a server for business users to test. So we are thinking of leveraging AWS (EC2) to setup a MobileFirst Server. However according to this tutorial, we need to purchse MobileFiest Server:
This tutorial is intended for use with MobileFirst Server, which is available for purchase from IBM.
We have already purchase a license for the production server but not for the testing server.
2) Which AMI (Amazon Machine Image) should we choose to run MobileFirst server?
1) Do we need to purchase additional license to test mobile first on AWS?
In order to install the MobileFirst Server on an external server (anything other than Eclipse), you must buy MobileFirst Platform Foundation from IBM.
2) Which AMI (Amazon Machine Image) should we choose to run MobileFirst server?
MobileFirst supports Linux in general, so you should be able to use any of those. Most popular I assume would be Ubuntu.
You may also want to check Amazon's community where users share images, and you may find there someone who shares an image for MobileFirst.