Multiple Jasperserver instances - multiple-instances

Need some help...
I have jasperserver 4.1 installed on my ubuntu. It runs via bundled tomcat server on 8080 port.
I've installed jasperserver 4.5 on the same host in different folder, and want them to run together. Second tomcat instance is listening on 8081 port.
The problem is when I log in (with the same credentials) via jasperserver web-interface at localhost:8080/jasperserver i am throwed out at localhost:8081/jasperserver and vice versa.
Repositories are different for sure.
Maybe jasperserver use some single auth mechanism?

I think it has something to sessions/cookie mechanism, because if i open them (localhost:8080/jasperserver, localhost:8081/jasperserver) in different browsers everything works ok.

Related

DB communication through proxy server

My problem looks like this:
A clientele has one, with a proxy, foreclosed network. However, they want to synchronize information (using odbc-connector) with a database server running on there own Linux server. Unfortunately, only very few ports are open and they do not want to open any further ports.
My idea is that I run the database communication over one of the open ports.
Since I've not done something like this so far, and I'm not really got any further with google search. So I was unfortunately not been able to change the default port of the database server in Plesk on e.g. Port 8080.
I'll be very happy about suggestions:
Either via help changing the port OR also over other ideas, how this problem could be solved more easily.
Thank you in advance!
The system in question looks as follows:
MySQL 5.5.55
Php: 5.6
Plesk Onyx 17.0.17
Ubuntu 14.04.5 LTS

crystal server 2013 installation on windows server 2008 64bit

When I run Tomcat configuration I get the error below.
Unable to open service BOEX140Tomcat.
Here is the error I get when I run SAP Crystal Server management
Here are the installed components of Crystal Report Server:
I would like to know what other software and components I need to install or what configuration changes I need to make .
apache tomcat for bi 4 automatically stop it self
[enter image description here][3]
and changed the config file inside tomcat to below
the apacha bi for tomcat services automatically get stopped in Central Configuration manager.
From your first screenshot, it appears that IIS is active on port 8080. If Tomcat has been installed along with Crystal Reports server and you've used the default port settings during the installation, then Tomcat will be configured to use port 8080 as well.
Only one process can bind to a given port. So as port 8080 is taken by IIS, Tomcat will stop and exit with an error. You can probably find the error message in one of the log files (check the log subfolder in the Tomcat installation folder).
Here's what you can do. Either:
Change the port Tomcat is using (as described here).
Change the port IIS is using (as described here).
Stop the IIS service if you don't need it (as described here)..

jboss as 7 - running multiple instances in the same linux server - standalone vs domain

I downloaded the jboss tar file.
Copied into my test server.
Did untar and installed it at $HOME/jboss/
Now, I need to have three instances running at the same time - Dev, QA, UAT - on a SINGLE server.
Is the Domain mode for this situation?
My conclusion was that it is not. That Domain mode is to manage JVMs across multiple servers.
For example, if I wanted QA to be in server1 and server2.
Is that correct?
However, my need is NOT to manage JBOSS instances across multiple servers.
Given that should I be using standalone mode?
If so, how would I run three instances of JBOSS (Dev, QA and UAT) concurrently.
I tried the instructions given here (Approach 2) : https://community.jboss.org/wiki/MultipleInstancesOfJBossAS7OnTheSameMachine
But I keep getting the errors like this:
MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use /127.0.0.1:9990
Is there any simple tutorial that I can follow.
I see this questions asked multiple times, but none of them seem to have a satisfactory answer.... that I find helpful. Is this a black art that lowly developers should not attempt in their home alone?
SGB
To get multiple jboss instances running on linux, in JBOSS_HOME/standalone/configuration/standalone.xml, I changed a single line from :
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
to the following...
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:100}">
NOTE:
The reason I was having problem was because I had setup my JBOSS_HOME in my .bash_profile as per the jboss installation instructions. I needed to remove this so that both instances would not use the same JBOSS_HOME.
Slight Change in above comment.
bash$ ./standalone.sh -Djboss.socket.binding.port-offset=10000
This will start the server port as 18080.
default port is 8080 + 10000 will give 18080.
It's easier to add "-Djboss.socket.binding.port-offset=1000" while starting standalone.sh, e.g.:
./standalone.sh -Djboss.socket.binding.port-offset=1000
This will start jboss on ports +1000 to the standard ones (so 8080 will become 18080). No need to change xml files.
If you are using Jboss on Intellij, you would like to add the offset into server configuration, just go to Run --> Edit configuration:

Remote access to MySQL on Amazon EC2 Windows instance

I found some solutions for Linux here.
But didn't find any solution for Windows. I don't have my.cnf on Windows. I only have my.ini. there is no bind-address in it.
I have already added an inbound rule for MySQL.
Could anybody give me some advice? Thanks a lot!!!
Here's what I would check:
Verify that the MySQL service is up and running by remote desktop'ing to the instance and trying to connect to it on the instance.
If that checks out, try modifying or disabling Windows Firewall to ensure that outside machines can connect on the relevant port. Depending on the Windows version, there might be several places that you need to fiddle with this (i.e. both Windows Firewall and Windows Firewall with advanced security).
If you're using an Asp.Net Application with Entity Framework, you will need to install the MySQL connector on the EC2 instance (I would suggest running iisreset to make sure the dll's are loaded).

Change port for TeamCity web server

I installed TeamCity and got it working against my project. However, I have since realized that I don't want it the administration page to be configured on port 80. I'm going to have other websites on that server that I want on the default port. How do I change the configured port?
I wandered around the configurations a bit and looked through the administration settings but couldn't figure it out.
The port number can be edited in the <TeamCity home>/conf/server.xml file, line <Connector port="8111" protocol="HTTP/1.1".
from Installing and Configuring the TeamCity server
To add to the answer provided by #sfussenegger you will also need to make sure that your build agents can still connect to the TeamCity server instance on the new port, or else your builds won't run.
To do this, you'll need to change the build agent configuration files to reflect the new serverUrl value. You can find this setting in the C:\TeamCity\buildAgent\conf\buildAgent.properties file.