We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
We are looking into way how to â€œcloneâ€ such an environment and produce a new environment, which is placed on different hosts but is identical to the old environment and most importantly, contains exactly the same metadata as the â€œoriginalâ€ environment. What we would like to do: â€¢ Copy IIS-relevant directory structure from the â€œoriginalâ€ services tier host to the â€œcloneâ€ service tier host â€¢ Copy IIS-relevant directory structure from the â€œoriginalâ€ engine tier host to the â€œcloneâ€ engine tier host â€¢ Clone â€œoriginalâ€ database with the metadata repository to the new database. â€¢ Get all the 3 tiers on new clone environments to work together through adjusting configurations and start the services
Obviously, the challenge here is to replace all the references to the â€œoriginalâ€ hosts and databases with the new ones, as well as changing passwords on the Metadata Repository. If the cloned environment would still manage to write into Metadata repository of the production environment, that would be fatal. There is IBM documentation present which describes changing host names, databases or passwords but it is generalized and we would really need concrete and specific documentation or tech notes on how to perform this cloning process.
Do not place IBM confidential, company confidential, or personal information into any field.