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.
Related
I am using new Mars 2 with esb tooling. I have added an local esb server with a carbon offset of 5. When I start run the server it starts correctly but the offset 5 does not have any impact none of the ports are incremented.
Starting the esb server from cmd works fine with offset.
Anyone else faced the same issue?
Here is the screen shot of the step while adding new server to eclipse, and I am giving the offset as 5. But when i start the server it starts on the 9443.
The screen you have attached, actually reads values from configuration files inside ESB and populates accordingly. So if you want an offset to your ports, then you should first change the following in <ESB_HOME>/repository/conf/carbon.xml
<Offset>4</Offset>
There after if you load the server configuration, you will see the Carbon server offset correctly reflecting as you have specified as below. The developer studio does not write values to files rather reads values from the them. So if a change is required to the default values, they should be first changed in the respective file.
New server dialog box
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
I am migrating my vCenter Server 5.5 to a new server (databases have already been moved to a new SQL server and all is OK on existing vCenter Server 5.5 implementation). When I begin the simple install process on the new vCenter Server host the Single Sign-On component presents me with an IP address of 10.10.10.117 as the ip address of the FQDN file01.xxxxxxxxx.com. This is the iSCSI interface address. I need it to use the 10.1.1.17 ip address that is the address of the production NIC that the ESXi 5.5 hosts will be communicating with. I have already changed the binding order of the NIC cards and flushed the DNS cache. I also added file01.xxxxxxxx.com with the proper IP address to the hosts file and also file01 to the hosts file. Still, during the install, 10.10.10.117 is discovered. Thanks in advance! Babak C.
Just to get a quick clarification...are you freshly installing vCenter 5.5? Or are you migrating an existing vCenter server to a new host and using the update utility to upgrade? I am assuming you are doing a fresh install based on your details about the SQL server and SSO. Here is my suggestion, in case it is a fresh install.
We had a similar problem with 5.5 on a new install where the IP address that was discovered during the actual vCenter Server install was that of the public facing NIC which we never use for management traffic (it's for internet access on the vC server, for update manager, etc.)
The strange thing is that there had NEVER been an entry in ANY of our DNS servers for that interface. So, after looking into it a little bit, I started thinking the IP that was returned during install was not a DNS result at all. Rather, it was (most likely) simply gathered from the interfaces on the Server based on binding order (e.g. which NIC has the default gateway.)
In order to save having to uninstall and clean up a major mess if the install completed wrong, we stopped and got in touch with VMware support. They suggested we clear all of the temporary files both in the standard "temporary" folder on windows as well as under /ApplicationData/vmware/xxx, where 'xxx' would be whatever product is giving you trouble and HAS NOT been FULLY INSTALLED* (e.g. you started the install and noticed the incorrect IP, so you terminated the installer and there is metadata and cached files remaining from the partially run install).
Basically, what we had to do, was clear the temporary files and then make sure the NIC Binding Priority was correct (so you should check in Network Adapters|(press-alt)|Advanced Settings. Make sure the correct binding is checked (e.g. if you don't use IPv6 on the private network, clear it) and make sure that the Windows Network is at the top of the priority list on the second pane of the advanced settings. This helps tremendously with SSO by making sure the Windows Network stack is the first queried when you are signing in and SSO must submit a kerberos ticket to the AD DC for validation.
It is possible, that once you delete the partial install files and temporary files and fix the network settings (probably be a good idea to reboot as well), the next time you run the installer you might have success.
I will try to check this post later to see if it helped you at all... or it I just succeeded in making your life even more difficult (which I certainly hope not!) :)
One more thing...prior to initializing the installer, open up a PS session, perform ipconfig /flushdns and then ping the hostname of your vCenter server in order to get it in the DNS cache. You should also perform the following:
nslookup
NS>{your vcenter server IP address}
/* make sure the resulting hostname is correct..this ensures your PTRs and rDNS is working correctly. vCenter HEAVILY relies on accurate reverse DNS configuration...then do the following lookup for forward DNS */
NS>{your vcenter server FQDN}
Hope it helps. Best of luck my friend!
SIETEC
If I want to ESB and API Manager in the same machine to which server I should set the CARBON_HOME? IF setting CARBON_HOME for one server is enough?
No need to set CARBON_HOME. You only need to set is JAVA_HOME. When carbon server starts up it automatically assigns it to its path. If you set CARBON_HOME manually you won't be able to run multiple servers on the same machine. If you have already set, remove it.
No need of setting CARBON_HOME but you must give different offsets inWSO2_SERVER_HOME/repository/conf/carbon.xml in each wso2 server.
<Offset>1</Offset>
default value is 0
CARBON_HOME Term means that your current servers directory.You can think of Just like JAVA_HOME. You can have one server in one machine by changing the port offset in carbon.xml located in HOME/repository/conf/carbon.xml
I am using BAM 2.2.0. I configured the service statistics toolbox inside the BAM server based on the documentation. And run the example program "service-stats"it is working fine.
But when I configure BAM inside my AS server using service data publisher configuration, and test the BAM server.Connection was established. But when I click the dashboard in BAM it shows an empty page with some msg how to configure AS .
Currently inside the BAM available script I can see "service-stats-271". How can I visualize my AS service status in BAM. Both servers are running in two machines.
Seeing "service-stats-271" is natural after installing the toolbox. But first you should see whether data has arrived to Cassandra from AS. For that you can login to Cassandra Explorer in BAM Management Console and see whether there is your column family existing in the EVENT_KS keyspace. If yes see whether there are any rows relevant to your events. If yes see whether the data has arrived to the H2 datbase during the execution of the Hive query.
If your data is not correctly published to Cassandra, please read [1] again. Sometimes you may not have done the following instruction mentioned there.
Go to <WSO2 Application Server home>/repository/conf/etc and open bam.xml file and enable ServiceDataPublishing as follows:
<BamConfig>
<ServiceDataPublishing>enable</ServiceDataPublishing>
</BamConfig>
[1] http://docs.wso2.org/wiki/display/BAM220/Setting+up+Service+Statistics+Data+Agent