Post

1 follower Follow
0
Avatar

How do we add a new cluster to the environment that's already discovered.

Hi, 

I would like to know how do we add new clusters to the environment that's already discovered.

we have few clusters that were added to the websphere admin console, and now I would also like them to be reflected in the deployIt. so id there a way we can add new clustered that can be automatically discovered.

 

 

Thank you 

Gsharma Answered

Please sign in to leave a comment.

12 comments

0
Avatar

There is no direct support for this in Deployit 3.9

However, there are some ways to make it work. Start out with the following steps

  • In the Infrastructure tab, find the WebSphere host. Next to the host, create a Directory called "New Discovery"
  • Duplicate the host  and move it into the New Discovery directory (Deployit 3.9) or recreate it inside the New Discovery folder (Deployit 3.8)
  • Run discovery on the host in the New Discovery directory. This will give you the current infrastructure. 

From this point, you have two options.

1. Migrate to the newly discovered infrastructure and environment

  • Create a new environment form scratch containing the topology from the "New Discovery" directory.
  • Undeploy all applications from the original environment and deploy them to the new environment.
  • After redeploying, discard the original environment and infrastructure, since they are no longer in use and move the WAS domain manager out of the New Discovery directory.

2. Update original infrastructure and environment

Another option is to manually synchronize the existing infrastructure and environment.

  • See what differences there are between the original topology and the newly discovered one. The Repository's compare function helps you to highlight the differences.
  • All new servers and clusters need to be manually added to the original WebSphere topology. You can use the CLI to copy CIs, by using the repository.copy() command. But take care that the new clusters no longer refer to servers in the New Discovery directory.
  • Finally, add the newly added infrastructure to the desired environments and update the deployments.

Hope this helps,

Hes Siemelink

XebiaLabs Support 0 votes
0
Avatar

Hi,

We use GUI, and not CLI. so I guess wont be able to do the 2nd option.

But apart from this, whenever we are doing a new discovery, we need the root password, and in our case, our system admins changes the root password, very often, and so getting the root password is a hassle, so Is there a way to connect instead of the root password.

 

Thanks

Gsharma 0 votes
0
Avatar

You can still use option 2, but in the second step you will have to manually recreate the CIs in the UI.

 

I'm not sure if I understand your question on the root password. What WebSphere user do you use for doing deployments, and can't you use that user for discovery? In any case for an update discovery would need the same credentials as an initial discovery, as it is essentially the same operation.

 

Kind regards,

    Hes Siemelink

XebiaLabs Support 0 votes
0
Avatar

Hi,

For initial and update discovery, we use the root username and password. And the root password gets changed every other day by the linux admin people. So is there a way to do discovery other than the root username and password. 

But once the Websphere is discovered we dont need the password to do deployments, then it works. But to do any update or new discovery, we need the root username and password.

Thanks

 

 

Gsharma 0 votes
0
Avatar

I think you need another user (that is not root) to do discovery. Check with the linux admin people is that's feasible.

Kind regards,

   Hes Siemelink

XebiaLabs Support 0 votes
0
Avatar

Hi,

We're pleased to announce that the feature to discover additional servers on an already discovered environment will be available in Deployit 3.9.2, which will be available shortly.

Kind regards,

   Hes Siemelink

XebiaLabs Support 0 votes
0
Avatar

Hi Garima

Hi, I have installed 3.9.2 now, how do I do automatic discovery?

Glad to hear! To update the WebSphere topology in Deployit, we can simply run the same discovery as we ran to originally discover the items again. In other words, right-click on the host on which the Deployment Manager is running, select Discover -> was.DeploymentManager, enter the required values and run discovery as normal.

When discovery has completed and it is time to save the discovered items, we can simply continue: items that are already in Deployit will be updated with the newly-discovered values. If we do not want this to happen and simply want to add the new items, we can remove all the other items from the list of discovered CIs.

Regards

Andrew

XebiaLabs

XebiaLabs Support 0 votes
0
Avatar

Thanks Andrew, 

 

But is there a way to save putting in the root password and username again and again to discover any item, Because when we do discovery, we need to get root username and password again and again.

so is there a way to save that.

 

 

Thanks

Gsharma 0 votes
0
Avatar

But is there a way to save putting in the root password and username again and again to discover any item, Because when we do discovery, we need to get root username and password again and again.

Is the problem here that we don't know the password to connect to the target machine, or that it expires? Whenever we need to interact with the WebSphere cell (whether doing discovery, deployments or whatever) we need to be able to log onto the machine where wsadmin is installed with an account that can execute wsadmin.

That definitely does not have to be the root account, but we do need to have valid credentials for some account on that system. Since it can invoke wsadmin, that account should also be sufficient to run discovery.

Regards

Andrew

XebiaLabs

XebiaLabs Support 0 votes
0
Avatar

Hi Andrew,

 

The username we connect to the target machine via root and it gets expired. so we have to rediscover everything again to get the missing ones in there now.

 

Also, we one more question when we are trying to rediscover a ci, to add the new ones in here, I  am adding all again, so the already deployed application would something effect them.

 

Thanks

Gsharma 0 votes
0
Avatar

Also, we one more question when we are trying to rediscover a ci, to add the new ones in here, I  am adding all again, so the already deployed application would something effect them.

Updating the infrastructure items will not affect any deployed applications. As described above, though, we can simply skip any updated items and simply keep the new ones, which avoids updates entirely.

The username we connect to the target machine via root and it gets expired. so we have to rediscover everything again to get the missing ones in there now.

Which username will we then use to connect to the machine to simply do application deployments? Could we use that to run discovery?

Regards

Andrew

XebiaLabs

XebiaLabs Support 0 votes