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 offering manager 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.
For product documentation, see Knowledge Center. Create and View Support Cases and Use the Discussion Forum here
We're working on configuring OpenPages 7 WebSphere with multiple servers. Investigation by our on-site IBM consultant has discovered that OpenPages segments servers as either an admin server or managed servers, which isn't called out in Chapter 14 with respect to Windows Server.
There also appears to be limitations surrounding the "admin server", specifically that you cannot build a redundant DR node.
Separate to this, there's also a WebSphere component called the Deployment Manager which is also only installed on the admin server, again not called out in Chapter 14. This also appears to suffer from the limitation of not being able to build the Deployment Manager capability into a second node for DR purposes.
I note there's an IBM article which talks about Deployment Manager HA (https://www-01.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/twve_xdsoconfig.html), but our advice from engineering is that we cannot have a secondary Deployment Manager node.
What we understand so far: a) The admin server controls synchronisation between itself and managed servers. Precisely what isn't clear. b) The admin server cannot be installed onto another server, to provide DR services. c) The admin server, should it require a rebuild, requires a rebuild of all managed servers (in our case up to three). d) The newly built managed servers cannot be attached to an existing admin server. e) There are HA options for the Deployment Manager, but we understand this isn't an option for the OpenPages implementation of WebSphere.
This enhancement is to: 1) Update the product offering (and documentation) to provide DR options for the "admin server". Backups alone aren't the answer.
2) Update the product offering (and documentation) to provide DR options for the Deployment Manager. Backups alone aren't the answer.
3) Update the product offering so that a rebuild of the "admin server" doesn't require a rebuild of every "managed server".
Do not place IBM confidential, company confidential, or personal information into any field.