We have an Apache where agent is pointing to sm12.0 version and we upgraded to sm 2.7.Now the question is re-registering the host(apache) with new sm12.7,is the below command is sufficient to re-register do we need any additional steps? Please advice.
smreghost -i policy_server_IP_address:[port] -u administrator_username -p Administrator_password-hn hostname_for_registration -hc host_configuration_ object
Thanks In advance.
smreghost command will remain same. There shouldn't be any issue with host registration.
There was no change in command in the 12.7 documentation. https://docops.ca.com/ca-single-sign-on/12-7/en/administrating/register-a-trusted-host-using-the-smreghost-registration-tool
Please find below another way using smreghost,
smreghost -i Policyserver IP Address -u user -p password -hn hostname -hc hostconfigname -f path_to_existing_host_config_file -o overwrite_existing_trusted_host.
If -o not used, existing trusted host must be deleted and then use smreghost command.
Thanks Krishna.How about if I have multiple policy servers because we have 3 policy servers.
You can manually add the remaining two Policysercer IP later in SmHost.conf or also use them while running smreghostb command
Could you please provide the sample for it which mean modify below to reflect multiple policy servers through command line rather editing in smhost.conf.
smreghost currently doesnt support multiple PS IP.
You can vote for this idea:
If multiple ps were used is it some thing below
smreghost -b 184.108.40.206 220.127.116.11 18.104.22.168 -u siteminder -p test@123 -hn <trustedhostname> -hc <HCO>
As long as all the policy servers are pointing to the same policy store or stores that replicate, you only need to reregister it once and either all the policy servers will use the new trusted host or if using multiple stores with replication, they will be copied over. You only need to run the smreghost on one Policy Server and make sure the new SmHost.conf file is written to the same location, as specified in your WebAgent.conf file, you should be fine. Also if your using multiple Policy Stores that replicate, it's best practice to write to one master Policy Store otherwise it could get confusing and multiple admins writing to different stores could overwrite each other's changes.