Install WSO2 ESB and Api Manager server in one server - wso2

I have to install both WSO2 ESB and API manager server in same development server. But always get Port already in use exception. I think that caused by the two apps using same JVM.
Could anyone please shed me light on proper configuration to make two server working tighter?

When you run multiple WSO2 products/clusters or multiple instances of the same product on the same server or virtual machines (VMs), you must change their default ports with an offset value to avoid port conflicts. An offset defines the number by which all ports in the runtime (e.g., HTTP/S ports) will be increased. For example, if the default HTTP port is 9763 and the offset is 1, the effective HTTP port will change to 9764. For each additional WSO2 product instance, you set the port offset to a unique value. The offset of the default ports is considered to be 0.
There are two ways to set an offset to a port:
Pass the port offset to the server during startup. The following
command starts the server with the default port incremented by
3:./wso2server.sh -DportOffset=3
Set the Ports section of <PRODUCT_HOME>/repository/conf/carbon.xml.
E.g., <Offset>3</Offset>
Refer Changing the Default Ports with Offset

Related

visualsvn cannot connect to WMI namespace the RPC server is unavailable

I did a lot of research for following matter and I got a lot of helpful information but the matter still remains, so I'm going to write it with full details
I'm trying to run "Remote Server Administration" with VisualSVN Server (Enterprise Edition), the server is Windows Server 2008 connected to the internet via router with port forwarding to this server. The client is not at local network so I use a static IP for the server.
Also I did every things written at this URL: http://www.visualsvn.com/support/topic/00025/
but I still get the following error message Connot connect to WMI namespace "..." : the RPC server is unavalible (0x800706ba) when I'm trying to "connecting to another computer".
On the other-hand, I can browsing the "Repositories" content by any web-browser successfully.
How can I manage the Repositories at remote servers?
"...the RPC server is unavalible (0x800706ba)" error indicates a connectivity issue to the remote machine.
Accessing WMI remotely requires port 135 TCP/UDP and all TCP ports above 1024 (1024-65535) to be opened (and forwarded), by default. You can setup fixed port for WMI to simplify the port-forwarding / proxy setup task. In order to setup the fixed port, follow steps described in the article "Setting Up a Fixed Port for WMI". After you follow these steps you are required to setup port forwarding and proxy rewrites (if any) for 135 TCP/UDP and port 24158 TCP.
"...Access is denied (0x80070005)" error indicates insufficient permissions to access WMI remotely. Add your user account to the local group on the remote machine: "Distributed COM Users".

Accessing a webservice on my localhost

I've a running WebService published on "http://localhost:8080/FreeMeteoWS/FreeMeteoWS?WSDL". I want to access this webservice from a device on the same network...what address should I put in order to retrieve the wsdl?
If that port i.e. 8080 is open for incoming connections on your computer you'd only need to find your local ip-address, this is done in different manners on different operating systems. When you have obtained local ip-address switch localhost out in favor for that ip-address.

location of cassandra.port in BAM2.2.0

I would like to monitor my application server application using WSO2 BAM. Intially I
didn't change the BAM offset address, keep it as by default(ie offset 0) and I changed the
application server offset as 2. It seems some problem to show. If I change the offset of BAM
server as 2. How can I change the cassandra.port address. I mean the location of the file in BAM 2.2.0 server.
Thanks
Cassandra port can be changed from wso2bam-2.2.0/repository/conf/etc/cassandra-component.xml.
But if you change BAM offset to 2, it automatically increases Cassandra port as well, unless you have enabled
<!--Nodes>localhost:9160</Nodes-->
entry in cassandra-component.xml.
If Lakmali's answer is not working properly apply the port offsets in,
All Hive scripts, if port numbers are used inside them. (Make sure you use DROP TABLE command before each Hive table's CREATE command, if you update the script in the same BAM pack without extracting a fresh pack.)
Cassandra port numbers in wso2bam-2.2.0/repository/conf/datasources/master-datasources.xml file.

The Cassandra Explorer cannot be connected when port is changed in BAM

When I apply a port offset in repository/conf/carbon.xml file of WSO2 BAM, connecting to the Cassandra cluster is failed. Is this a known bug or should I change some configuration?
Make sure you enter the correct connection URL. The example URL next to the connection URL text box is correct only for the zero port offset BAM server. Add the port offset to the port number mentioned in the sample connection URL when entered.
You need to use the correct Cassandra port if you have changed the port offset. New Cassandra port value will be (9160 + port offset).
Hope this helps.

Sharing port 443 between IIS and a C++ service

Because of a certain requirement i need to have a service listening on port 443 (an maybe 80) to coexist with IIS on a same windows 2008 server. Its possible to have a Windows Service Hosted WCF service to share port 80 with IIS but i was wondering if this is possible to do in a C++ service? I've read answers about similar questions like this, this and this but i still haven't got an appropriate answer.
Only one application may be bound to an ip-address/port-number pair. If a socket is bound to INADDR_ANY and some port, then no other application my bind to that port.
If you want two applications to receive data on a port, you need some kind of proxy that listens on the actual port, while the other programs listens on some other port or address that the proxy-server connects to.
Using a proxy seems to be the way that WCF handles port-sharing. Quote from this link:
When a net.tcp binding enables port sharing (by setting portSharingEnabled=true on the
transport binding element), it implicitly allows an external process (namely the
SMSvcHost.exe, which hosts the Net.TCP Port Sharing Service) to manage the TCP socket on
its behalf.