We are in process to replicate Jira prod which is running behind a reverse proxy to another test server with same configuration should be reflect here.version 7.1.9, windows 2012, MSSQL DB.
Hi Vivuu,
I attach a reference to the Atlassian documentation describing how to set up a JIRA test environment.Be sure to make a copy of your production database (with a different name) and connect it to the JIRA test environment.
Best Regards
Pavel
MoroSystems Support
We followed the steps and , after restoring everything from Prod (DB, Home flder) In Test server, We have noticed that the test environment has been taken the same license from PROD.
So we are worrying about where it got the link with PROD still now and will it impact anything.Why the test environment license is not reflecting and what we have to do now here without making any change to PROD
Yes, it's as you say - it's a complete clone.
You do not have to worry, the production license for the test environment will not cause malfunction or interconnection of the production system. However, because of Atlassian licensing terms, a special license (free of charge) must be generated for the test environment.
The only problem can be in the application links if they are linked to other Atlassian applications. You need to delete them and connect them to the test environment.
Please note the following information (the information is written in the above procedure), particularly paragraphs 1., 4. and 5.
Post-startup modifications
1. Modify the instance colors. See Configuring the look and feel of your JIRA applications. This is a good practice for users to identify that they're on the staging server.
2. Modify the instance base URL. See Configuring JIRA options and change the Instance URL to the staging URL.
3. Consider the URL whitelist. You may wish to change some of the approved URLs. See Configuring the whitelist.
4. Apply a development license. See our licensing FAQ to generate a license for the staging server. Refer to Licensing your JIRA applications to apply it.
5. Reconfigure applinks. If you are connecting to other servers via applinks, you'll need to change the server ID for those instances.
If you leave applinks in place, it's possible to have your production instance point back to the staging server, if a link is generated.
Thanks !!
But here in our infra , the Jira is already licensed and we dont have the Atlassian account of that to get the developer license for the test environment.
Can you please advise, How can get the Developer license for the Test environment by using the PROD license Sen-key
We have migrated all our applications, Crowd, Jira, Bitbucket, Confluence to Test environment from Prod Servers.(By application data and DB data store to Test environment)
But , The application integration to Test Crowd and between Test applications how can make to Test Configuration for these applications, without affecting PROD
1)Test Crowd Should authenticate all test environemnt applications (Currently test crowd containing map with Prod application IP Addresses)
2)How The integration Between These applications in test environment can be replaced to Test application integration by removing PROD links
Since Production Data are copied and DB are restored, Now test applications will be having old trace with the production instances. How to revert it with test instances and what are the files need to be edited for enabling the integration
1) In the Crowd setting, you need to customize the configuration itself for specific applications (setting Remote addresses for test servers or creating a special test group with special users, etc.). Please look at the Crowd documentation Crowd Administration Guide
2) Just delete the current application links and re-create them for the test environment. All Atlassian applications will then only communicate with the test environment.
It looks like you're new here. Sign in or register to get started.
