IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Ability to rename a windows server nodename or add an additional "alias" node name of sorts

In our environment we came up with the decision to use an alias node naming convention, where our customers create an alias address for a Connect Direct server i.e We take the alias-name part and use that as the Connect Direct node name. When the customers’ servers are upgraded, we install Connect Direct on the new replacement server and give it the same alias name as the server it is replacing, and when the customer’s server goes live we will repoint the alias address from the old server to the new server. We did this in order to ensure the vast number of our users no longer have to worry about having to change the node names in their .cdp files, JCL, and bin files when they move to their new server.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 27 2019
  • Declined
How will this idea be used?

Connect Direct Application support staff will be able to setup an automated puppet install package for deployment to customer's new servers. Post install, app support staff will either be able to rename node name or add second/alias node name on server. App support staff will configure user setup. User import existing scripts, cdps, bin files and run jobs on normal schedule.

What is your industry? Insurance
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Admin
    Chris Sanders commented
    July 15, 2019 17:04

    Thank you for opening this enhancement request with IBM. I have reviewed it thoroughly with my team. Unfortunately we will need to decline the request due to the technical impact that it would have. The node name that is chosen during installation is used in multiple areas such as setting up the service that C:D runs under, in the DB, registry, statistics, and other areas. Trying to change these after installation has a potential to cause unnecessary defects so we can't justify making this change.

    I did want to make sure that you are aware that the nodename can bet set by using the Custom installation option however. The default nodename is the hostname of the machine, but by chosing the custom option you can set it to whatever you would like. This should give you the opportunity to proactivly set the nodename to whatever you'd like it to be when the server is deployed.

    Thank you for opening this request and I'm sorry that I couldn't accept it. Please don't hesitate to use the tool again in the future should you have other ideas that we could explore.


    Chris Sanders

    Connect:Direct Offering Manager