Hello Experts,
Could anyone provide me the exact steps for changing documentum content server host name?.
Thanks in advance
you need to apply the following fix after you change the hostname
If the IP address or hostname of content server is changed, we need to apply the following hotfix
ftp://dev_pre:qa5.grN6@ftp2.lss.emc.com/sustaining/Content_Server/Archives/6.0/Bug147071_pre60SP1_engr_fix.zipqa5.grN6@ftp2.lss.emc.com/sustaining/Content_Server/Archives/6.0/Bug147071_pre60SP1_engr_fix.zip
also dm_server_config objects.
Does not pretend that following places where hostname is stored are full:
1. server.ini in dba/config/<docbase>/
2. start/stop docbase and docbroker scripts in dba/
3. acs.properties in server/DctmServer_MethodServer/deploy/acs.ear/lib/configs.jar/config/
4. object_name, acs_base_url, projection_targets in dm_acs_config
5. object_name, base_uri, projection_targets in dm_jms_config
6. r_host_name in dm_server_config (seems to be updated when repository started)
7. web_server_loc in dm_server_config
8. host_name in dm_mount_point
9. target_server in dm_job
I did it but when I start JMS it searches for the old host. In fact 99% of the things are working properly except that jms creates a file in E:\Documentum\jboss5.1.0\bin with name message.
TEST_9084_status_output
======================================================================
14:06:22,778 ERROR [Twiddle] Exec failed
org.jboss.util.NestedRuntimeException: Could not obtain connection to any of these urls: test:9084; - nested throwable: (javax.naming.CommunicationException: Could not obtain connection to any of these urls: test:9084 [Root exception is javax.naming.CommunicationException: Failed to connect to server test/192.168.10.10:9084 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server test/192.168.10.10:9084 [Root exception is java.net.SocketException: Permission denied: connect]]])
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:144)
at org.jboss.console.twiddle.command.MBeanServerCommand.getMBeanServer(MBeanServerCommand.java:59)
at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:149)
at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:306)
Caused by: javax.naming.CommunicationException: Could not obtain connection to any of these urls: test:9084 [Root exception is javax.naming.CommunicationException: Failed to connect to server test/192.168.10.10:9084 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server test/192.168.10.10:9084 [Root exception is java.net.SocketException: Permission denied: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.console.twiddle.Twiddle.createMBeanServerConnection(Twiddle.java:251)
at org.jboss.console.twiddle.Twiddle.connect(Twiddle.java:269)
at org.jboss.console.twiddle.Twiddle.access$300(Twiddle.java:63)
at org.jboss.console.twiddle.Twiddle$1.getServer(Twiddle.java:140)
... 3 more
Caused by: javax.naming.CommunicationException: Failed to connect to server test/192.168.10.10:9084 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server test/192.168.10.10:9084 [Root exception is java.net.SocketException: Permission denied: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:335)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1734)
... 10 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server test/192.168.10.10:9084 [Root exception is java.net.SocketException: Permission denied: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:305)
... 11 more
Caused by: java.net.SocketException: Permission denied: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:529)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:97)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:82)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:301)
Where Test is the old name of the host and the ip address is also not valid it has been changed to 192.168.10.12
Hello PanfilovAB,
I have done all of the steps already, but still don't know where the jms finds the old host name.
One thing I have observed is that, if I shutdown Docbase and start jms the file is created without error message, just with a boolean value "true".
If I start docbase it is created with that error. So, I think, it stores the host name in docbase, but where?
I have also applyed the bug fix but no luck.
I had never run documentum software on windows platform.
If you are on windows, check the account on which the service is running on.
