I understand you need a guide for replicating your Production Crowd server in a Test environment. I hope it is to test an upgrade. :)
We have an article on how to create a test environment for Crowd:
Please review it and let us know any questions that arise. We are happy to answer.
We follwed the below steps and getting error.
1)Installed fresh instance of crowd in test environment.
2) Copied the Crowd home directory to the Test Environment
3) restord the Prod DB in Test SQlDB
3) Edited the crowd.config .xml to point the test DB
4?) Restarted the Crowd service.
But we are getting below error
"HTTP Status 404 - /crowd
type Status report
description The requested resource is not available.
Thanks a lot for fixing the issue..
Now we may need assistance here.
We have migrated all our applications, Crowd, Jira, Bitbucket, Confluence to Test environment.
But , The application integration to Crowd and between applications how can make to Test Configuration for these applications, without affecting PROD
Is there anything in particular you would like to ask about this replication?
In general Crowd does not actively connect to applications connected to it, so the test replica should not affect your working production environment.
Once you have your testing environment, I encourage you to try the newest Crowd 3.0.1 version on it.
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 environment 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
To make the Crowd instance "talk" to the test applications, please set up the test applications as described on this page: Adding an Application
Likewise, the Applications menu in Crowd is where you would remove the Production applications.
Now Our Prod setup-Crowd-2.11.1 in Windows server and it should be migrated to linux machine in another domain with a different url .
currently in windows the atlassin application are running behind reverse proxy and for authentication we are using crowd internal directory ?
So please let us know what are the steps need to be implemented for data migration to new instance in the linux (windows to linux )
using MSSQl DB in both environment
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs