Académique Documents
Professionnel Documents
Culture Documents
GU_20121228_030
Contact person
Ma Chunxin
Deadline
2013-1-15
Applicable product
GU-OMCB
Applicable software
OMCBV4.11.10.14P05
version
Notice
Execution
classification
Notification
Contact number
+86-18621908932
Applicable
hardware version
Issued to
Operator
All
Notice of Solution to the Problem of Some Parameters Cannot Be Left Unconfigured in CMX
1/4
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
2.
Overwrite the files in the above directories on the client with the attachment, clear the
\ZX-OMMB\ums-clnt\temp directory, and restart the client.
Stop OMMB server. Ftp the attached file to the server in bin mode. Unzip the file and
replace the following files on the server and client respectively.
ums-svr\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-svr\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
2.
Delete all the temporary files in the ums-svr/temp and ums-clnt/temp folders. Restart
the server.
3.
Click the Force to Upload button to upload the OMMB client files to EMS client.
Note: Replace all the OMMBs connected to EMS before executing Force to Upload. Otherwise,
the OMMB client connected to EMS may be the one not replaced.
Master/Slave SBCX
1.
Log in to the slave SBCX, and ftp the attached file to the above mentioned directory of the
slave SBCX in the bin mode.
2/4
2.
Stop the OMMHOST of the slave SBCX and replace the following files on the client and
server respectively.
ums-svr\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-svr\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
3.
4.
Log in to the master SBCX, and ftp the attached file to the above mentioned directory of the
master SBCX in the bin mode.
5.
Stop the OMMHOST of the master SBCX and replace the following files.
ums-svr\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-svr\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-common-api.par\mediatorsdrmap-common-api.jar
ums-clnt\zxomcb\MEDIATOR\SDRMAP\mediator-sdrmap-commonapi.par\conf\mediator-table-operator.xml
6.
7.
Start the OMMHST on the master SBCX. Log in to the slave SBCX, and start the
OMMHOST of the slave SBCX (by the telnet command from the master SBCX through
the master/slave channel or by local access).
3/4
8.
Click the Force to Upload button to upload the OMMB client files to EMS client.
Note: Perform Force to Upload after all the zipped packages on OMMB connected to EMS are
replaced. Otherwise, the OMMB client connected to EMS may be the one not replaced.
Rollback Solution
Copy the backup file back to the original directory and replace the file with the same name.
Attachment:
GUOMCB4.11.14P05p
atch.zip
Ma Chunxin
Date
2012-12-25
Reviewed by
Chen Taiming
Date
2012-12-26
Approved by
Zhang Zhongqi
Date
2012-12-27
Issued by
Sun Jingjing
Date
2012-12-28
4/4