_MigrateServerXML
Locate your
server.xmlfile.
Tell me where to look...Release Directory Stash 3.7 and earlier <Stash installation directory>/conf/server.xmlStash 3.8 and later <Stash home directory>/shared/server.xmlBitbucket Server 4.0 - 4.14 <Bitbucket home directory>/shared/server.xmlBitbucket Server 5.0 and later N/A, replaced by <Bitbucket home directory>/shared/bitbucket.propertiesIdentify and note any customizations made. Ideally you will know which customizations were made and can locate them in your
server.xmlfile.
Here are some common customizations...This is not a comprehensive list. Review your
server.xmlfile closely to ensure all your customizations are noted.Securing Bitbucket using SSL.
- Running Bitbucket behind a reverse a proxy.
- Bypassing the Bitbucket reverse proxy to solve Application Links issues.
- Bypassing the Bitbucket proxy to connect directly to a Data Center node (for troubleshooting, or to generate support zips).
- Configuring a custom keystore path and password.
- Locate your
bitbucket.propertiesfile in the<Bitbucket home directory>/shareddirectory. - Look up the customization equivalent in the
bitbucket.propertiesfile by referring to one of the migration examples and/or by using the migration table below. Add the equivalent values to the
bitbucket.propertiesfile. Save and close the file.For Bitbucket Data Center users...The value for your load balancer to support session affinity ("sticky sessions") was previously set to
JSESSIONID. The default value for Bitbucket 5.0+ has changed toBITBUCKETSESSIONID.You need to either change your load balancer cookie configuration to
BITBUCKETSESSIONID, or, change the value in thebitbucket.propertiesfile toJSESSIONID.To change the value in the bitbucket.properties file, add this line
server.session.cookie.name=JSESSIONIDTo change this value in your load balancer configuration, locate your load balancer proxy configuration file, change the instances of
JSESSIONIDtoBITBUCKETSESSIONID.- Remove or rename the
server.xmlfile (don't delete this file until you confirm the customizations were successfully migrated to your upgraded instance).
Migration reference table
4.x and earlier (server.xml) | 5.x and later (bitbucket.properties) |
|---|---|
compression="on" | server.compression.enabled=true |
compressableMimeType="text/html,text/xml,text/ | server.compression.mime-types=text/css,text/html,text/javascript,text/application/javascript,application/ |
connectionTimeout="20000" | server.connection-timeout=20000 |
path="/" | server.context-path=/ |
| N/A | server.displayName=Atlassian Bitbucket |
port="7990" | server.port=7990 |
useHttpOnly="true" | server.session.cookie.http-only=true |
secure="true" | server.secure=true |
SSLEnabled="true" | server.ssl.enabled=true |
keyAlias="YourAlias"
| server.ssl.key-alias=tomcat |
keystoreFile=
| server.ssl.key-store= |
| server.ssl.key-store-password=changeit |
sslProtocol="TLSv1.2" | server.ssl.protocol=TLSv1.2 |
keystoreType="JKS"
| server.ssl.key-store-type= |
| server.ssl.client-auth=want or server.ssl.client-auth=need |
redirectPort="443" | server.redirect-port=443 |
proxyPort="443" | server.proxy-port=443 |
proxyName="mycompany.com" | server.proxy-name=mycompany.com |
address="192.168.10.10" | server.address=192.168.10.10 |
For Bitbucket Data Center
These properties are applicable to Bitbucket Data Center instances. In previous versions these were set within load balancer configuration files. Depending on which load balancer you're using, there are many configuration options, so it is not possible to precisely describe the properties or values for every configuration.
Setting these values within the bitbucket.properties in file in 5.0+ overrides what's in the load balancer configuration file.
server.session.cookie.name=BITBUCKETSESSIONIDserver.session.timeout=1800server.session.tracking-modes=cookie
Related content
- No related content found