hpdp-as service - after changing the domain name on the Cell Server, the service continues to use the old name.`

Hello.

Customer change domain name for CS - for example from cs.domain1.com to cs.domain2.com - using command "/opt/omni/sbin/omnicellnamechange.pl --newcmhost ".

After that Data Protector successfully started and working. Data Protector release 10.30.

But if you display a list of java processes, you can see that the old domain name is used in the application server start options.

# ps =ef-ef|grep java
root 2059 1 0 Jul27 ? 00:00:00 jsvc.exec -java-home /opt/omni/jre -cwd /opt/omni/bin/telemetry -cp /opt/omni/bin/telemetry/commons-daemon-1.0.15.jar:/opt/omni/bin/telemetry/telemetry-client-service.jar:/opt/omni/bin/telemetry/commons-logging-1.1.2.jar:/opt/omni/bin/telemetry/fluent-hc-4.5.2.jar:/opt/omni/bin/telemetry/httpclient-4.5.2.jar:/opt/omni/bin/telemetry/httpcore-4.4.4.jar:/opt/omni/bin/telemetry/jackson-annotations-2.7.0.jar:/opt/omni/bin/telemetry/jackson-core-2.7.0.jar:/opt/omni/bin/telemetry/jackson-databind-2.7.0.jar:/opt/omni/bin/telemetry/log4j-api-2.6.2.jar:/opt/omni/bin/telemetry/log4j-core-2.6.2.jar:/opt/omni/bin/telemetry/jjwt-0.7.0.jar -user root -outfile /var/opt/omni/log/telemetry/install-telemetry-client-service-stdout.txt -errfile /var/opt/omni/log/telemetry/install-telemetry-client-service-stderr.txt -pidfile /tmp/dataprotector-telemetry-client-service.pid com.hp.im.dp.telemetryclientservice.App
root 2060 2059 0 Jul27 ? 00:00:25 jsvc.exec -java-home /opt/omni/jre -cwd /opt/omni/bin/telemetry -cp /opt/omni/bin/telemetry/commons-daemon-1.0.15.jar:/opt/omni/bin/telemetry/telemetry-client-service.jar:/opt/omni/bin/telemetry/commons-logging-1.1.2.jar:/opt/omni/bin/telemetry/fluent-hc-4.5.2.jar:/opt/omni/bin/telemetry/httpclient-4.5.2.jar:/opt/omni/bin/telemetry/httpcore-4.4.4.jar:/opt/omni/bin/telemetry/jackson-annotations-2.7.0.jar:/opt/omni/bin/telemetry/jackson-core-2.7.0.jar:/opt/omni/bin/telemetry/jackson-databind-2.7.0.jar:/opt/omni/bin/telemetry/log4j-api-2.6.2.jar:/opt/omni/bin/telemetry/log4j-core-2.6.2.jar:/opt/omni/bin/telemetry/jjwt-0.7.0.jar -user root -outfile /var/opt/omni/log/telemetry/install-telemetry-client-service-stdout.txt -errfile /var/opt/omni/log/telemetry/install-telemetry-client-service-stderr.txt -pidfile /tmp/dataprotector-telemetry-client-service.pid com.hp.im.dp.telemetryclientservice.App
root 12265 19602 0 11:53 pts/1 00:00:00 grep --color=auto java
hpdp 25093 25013 4 10:14 ? 00:04:20 /opt/omni/jre/bin/java -D[Standalone] -server -Xmx2048m -Xms2048m -Xss228k -XX:NewRatio=2 -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=512m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.as.management.blocking.timeout=1200 -Dorg.jboss.boot.log.file=/var/opt/omni/log/AppServer/boot.log -Dlogging.configuration=file:/etc/opt/omni/server/AppServer/logging.properties -Djboss.server.log.dir=/var/opt/omni/log/AppServer -Djboss.server.temp.dir=/var/opt/omni/tmp/AppServer -Djboss.server.data.dir=/var/opt/omni/server/AppServer -Djboss.server.config.dir=/etc/opt/omni/server/AppServer -Dhp.dataprotector.programdir=/opt/omni/bin -Dhp.dataprotector.lbindir=/opt/omni/lbin -Dhp.dataprotector.sbindir=/opt/omni/sbin -Dhp.dataprotector.datadir=/var/opt/omni -Dhp.dataprotector.configdir=/etc/opt/omni -Dhp.dataprotector.shared.datadir=/var/opt/omni -Dhp.dataprotector.shared.configdir=/etc/opt/omni -Dcom.hp.im.components.configdir=/etc/opt/omni/client/components -jar /opt/omni/AppServer/jboss-modules.jar -mp /opt/omni/AppServer/modules org.jboss.as.standalone -Djboss.home.dir=/opt/omni/AppServer -Djboss.server.base.dir=/opt/omni/AppServer/standalone -b cs.domain1.com

The customer uses the legacy  scheduler and therefore does not use the Home tab. But we are preparing to upgrade to version 10.90 and I think that this fact may hinder us.

How can I make changes to the application server start command line to use the correct server name?