This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

Video



If we take a copy of a production system and wish to install it as a development/test system, there are a number of areas we need to modify to prevent the test/dev system from connecting to the production  AR Server/Mongo/Openfire/Smart IT backend database etc.

The recommendation would be to uninstall Smart IT completely on the duplicated environment and perform a fresh Smart IT/MyIT Installation using the new server names. The following link gives detailed steps on uninstalling the product:-
     https://docs.bmc.com/docs/display/public/myit33/Uninstalling+Smart+IT+and+MyIT


Alternatively, the AR Server name must be modified in the following areas:-

- SmartIT_System.CONFIGURATION_PARAMETER table (contains the hostname/port/Rapp Password) in the Smart IT SQL database.

- SmartIT_System.PROVIDER_SETTINGS table (check for entries where 'KEYNAME' like '%host%' )  in the Smart IT SQL database

- In Mid-Tier, navigate to BMC MyIT Administration-> MyIT Adminstration Console - you will see the old server listed on applications 'BMC MyIT', 'MyIT-ITSM' and 'MyIT-HRCM'
     - Create an entry for your new AR Server in 'Persistent Data Stores'
     - On the 'Applications' section, update 'BMC MyIT', 'MyIT-ITSM' and 'MyIT-HRCM' to use the new server entry
** if you are using 18.05 and above perform this change on form SMT:Administration Console

- In Mid-Tier, open the SHR:SHR_KeyStore form and set the 'Host Name' to the correct value to connect to the cloned Smart IT host. Since this is stored in the AR System database and since a copy of this database will be used on the cloned system, this will be initially pointing to the production Smart IT server.  If we do not change this to point to the cloned Smart IT instance, Social Bridge records on the cloned system would be sent to the production Smart IT instances.


The Mongo server names/settings should be checked/updated:-

- In  <SmartIT_Install_Dir>\social, check hostnames/IP Addresses for Mongo servers in 'config.js' file and update "db_host", "db_username", "db_pw" lines as appropriate for the Mongo DB used for this cloned system. These must not point to the production Mongo DB replica set.
** if you are using 18.05 and above this change can be ignored

The Openfire chat parameters need to be checked/updated:-

- The 'connect.properties' file (<SmartIT_Tomcat_Install_Dir>\external-conf directory) contains a number of references to the MyIT Server name and Openfire connection details:

   myit.server.host = myserver-011                                
  chat.server.cm.host = myserver-011                           
  ...
  ...
  chat.server.boshUrl = http://myserver-011:7070/http-bind/      
  chat.server.domain = myserver-011                              

- Update the '<serverURL>' to point the Openfire instance(s) to the correct SQL database instance fort he cloned environment.

- Within the Openfire Console->Server Manager->System Properties, the following parameters need to be checked/updated:
   xmpp.domain - This must match the 'chat.server.cm.host' parameter in 'connect.properties'
   provider.auth.authResource - This will need to be altered so that it references the new hostname/load balancer for the cloned Smart IT instance(s)
   admin.authorisedJIDs - modify to match the cloned Openfire xmpp.domain

- If using Openfire with SSL, add suitable SSL certificates under the TLS/SSL Certificates tab
- If using Openfire with SSL, add the new Openfire SSL certificates for the cloned system in the cacerts file within the JRE /lib/security directory for the JRE used by the cloned Smart IT instance(s).
- If using the HazelCast Plugin for Openfire clustering, update the 'member' entries in the <Openfire_install_dir>\openfire\plugins\hazelcast\classes\hazelcast-cache-config.xml to match the cloned Openfire instances.


Some other Smart IT related parameters to update:-
- The ux.xml file (<SmartIT_Tomcat_Install_Dir>\conf\Catalina\localhost directory) contains references to the JDBC connection to the SmartIT_System and SmartIT_Business schemas:
** if you are using 18.05 and above the file ux.xml file name is now called smartit.xml

- Within this file there will be references to the JDBC database connection - (this is from a system connecting to MSSQLServer db):-

                 url="jdbc:jtds:sqlserver://mydbserver-011:1433/SmartIT"

- NOTE: There will be two such references. The db username/passwords for this connection are also in this file.

- If using SmartIT with SSL, add suitable SSL certificates to a keystore file to be referenced within the SmartIT Tomcat server.xml file.

Make sure that you do not have any extra/backup ux.xml files in the <tomcat>\conf\Catalina\localhost

- Backup and Update C:\Program Files\BMC Software\Smart_IT\Smart_IT\filedeployer\arfileDeployer.properties

    Replace all <old host short name> with <new host short name>


See also: BEST FAQ on Remedy for Smart IT Connectivity Issues