Migrating from Single server to Enterprise topology - looking for guidance
Our current installation is single server, built in Websphere Liberty and classic built in user registry. We have a need to move to a more stable environment which means we also need to move to an enterprise topology.
I see lots of materials on moving from one environment to another but they don't distinguish moving from single to distributed servers. There also appears to be a pre-req that a distributed environment cannot be built in Websphere Liberty but now needs to be full blown Websphere application servers and also a requirement to move from the built in user registry to either LDAP or to a federated file structure.
Can any of the developers online please assist with any materials that I need to be looking at to do this. The interactive installation guide helps but it doesn't cover off the splitting out, or the installation of and setup of Websphere for the new environment etc.
Other question as well is that we don't want to move all projects from the old system - is there a way to filter out what is moved - we don't want to take unnecessary baggage with us.
Thanks in advance.
2 answers
Karen, we have created this for this purpose: https://jazz.net/deployment-wiki-home.jsp
Can you quantify "If you can then use Linux as it makes slightly better use of resources"
Comments
Hi Gerald,
It seems most performance tests on https://jazz.net/wiki/bin/view/Deployment/PerformanceDatasheetsAndSizingGuidelines are exclusively run on Linux OS. But if you are already on Windows Servers, have your scripts and environment set up I would probably stay.
Comments
Ulf Arne Bister
Feb 06 '19, 10:04 a.m.Also of interest: what Jazz environment do you currently have? Full CLM on one server? LQE, JRS in the mix? If you can then use Linux as it makes slightly better use of resources - but also requires a bit more admin know how. There is no comprisive guide to splitting a single server install into an Enterprise Topology but if I find a few cycles I will sketch the outline. Done it in the past, not all that hard.
Removing archived projects is not entirely support as of now over the entire CLM lifecycle. This would require the same changes as needed for splitting them off or truly archiving. Suggestion: backup, script removal of what you can, move.
Karen Steele
Feb 06 '19, 10:51 a.m.Alf, thanks for your quick response. We are current full CLM on one server (with exception of the JRS).
All help greatly appreciated, we don't want to go full Websphere if we can help it - but then again we don't want to cause login to each server, each app still has to be able to communicate with RQM/RTC/Doors etc.