Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Configuring server.xml after "splitting" the server Edited

Hi All, 

 

We used to run both Jira and Confluence in a single VM. Now we decided to split the applications to their own VMs. Splitting was done by cloning and renaming the second VM, and disabling Confluence from the first VM and Jira from the second. 

 

Now I need to figure out how to configure the server.xml so that jira can be found at jira.company.com and confluence from confluence.company.com. 

 

I tried to check the original server.xml's but I could not figure out how to change them. 

Bellow is the current Server.xml for confluence ( Https is not required ):

<Server port="8000" shutdown="SHUTDOWN" debug="0">
<Service name="Tomcat-Standalone">
<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol" />

<Engine name="Standalone" defaultHost="localhost" debug="0">

<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">
<Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">
<!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties -->
<Manager pathname="" />
<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />
</Context>

<Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0" reloadable="false" useHttpOnly="true">
<Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />
</Context>
</Host>

</Engine>

<!--
To run Confluence via HTTPS:
* Uncomment the Connector below
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and the keystore itself.
* Restart and visit https://localhost:8443/

For more info, see https://confluence.atlassian.com/display/DOC/Running+Confluence+Over+SSL+or+HTTPS
-->

<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"
protocol="org.apache.coyote.http11.Http11NioProtocol"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
clientAuth="false" sslProtocols="TLSv1,TLSv1.1,TLSv1.2" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" SSLEnabled="true"
keystoreFile="D:\Confluence\conf\Security\keystore_2018.jks"
URIEncoding="UTF-8" keystorePass="XXXXXXXXXXXX"/>

</Service>
</Server>

 

1 answer

1 accepted

1 vote
Answer accepted

Hi @Carl Wiedebaum,

The server.xml file configures, on which ports the tomccat listens, which protocols are used, and if an proxy is used and such things.

That Jira.company.com leads to Jira and confluence.company.com leads to confluence is configured within your DNS configuration, where you configure what (sub)domain leads to which IP.

Hi @Bastian Stehmann _neusta portal services_,

The DNS configuration is already made so that confluence.company.com leads to the actual confluence server.  but since the confluence is "cloned" from the original server, confluence can only be accessed at https://confluence.company.com:8443.

 

What I want to achieve is that confluence.company.com works for confluence - just like at the moment jira.company.com works for jira. 

 

My initial assumption was to change:

<Connector port="8443" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"


to:

<Connector port="80" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25"

 

What confuses me that in the currently working as intended Jiras server.xml there is also specified the domain name, but corresponding setting in the confluences server.xml can't be found. 

Ok, got it.

You are right, changing the port should do.

There is no need to have the server name there.

Edit: if you do not want to use SSL, I would comment that connector out.

 

So I fully comment the SSL connector out and from the first connector: 

<Connector port="8090" connectionTimeout="20000" redirectPort="8443"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol" />


I change the port 8090 to 80 and remove the "redirectPort" section? So the end result would look like: 

<Connector port="80" connectionTimeout="20000"
maxThreads="48" minSpareThreads="10"
enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
protocol="org.apache.coyote.http11.Http11NioProtocol" />

 ?

Yes, I think that looks good to me.

Like Carl Wiedebaum likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

247 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you