Managing the app server in Developer Edition

I've got Developer Edition (6.6) installed on my computer (running XP Pro SP3).

I've got two questions regarding the administration of it.

1) Often, when developing custom webtop apps, there is a requirement to restart the app server, for instance, when there is a change in NLSProp.properties files. How does one do this with the developer edition? I see 4 Documentum items in my services menu: Documentum Docbase Service documentum, Documentum Docbroker Service Docbroker, Documentum Java Method Server, and Documentum Master Service. I know that Documentum Master Service is used to start up the whole shebang, but it turns itself "off" after starting up the other 3. Oddly enough, I sometimes notice that the Java Method Server also seems to turn itself off (at least as displayed in the Services menu).

Anyway, How do I restart the webtop app server on the Developer Edition?

2) When I was installing the developer edition, I was moving a little too fast, and didn't quite take note of the passwords being entered. As a result, I can't access the JBoss admin screen. I know the installation guide says: "The JBoss administrative user name is "admin" and the password is "oem_repositoryOwnerPassword". By default repositoryOwnerPassword is documentum-1, making the default JBoss admin password oem_documentum-1." For whatever reason, that doesn't work. I don't know who the repositoryOwner is, and I don't know the password. I figure since this installation is sitting on my own computer, there has to be a way to recover or reset this password. Also, since this installation is for me only, and I'm not sharing it with anyone else, I don't need a lot of security on it, so if we could revert to the plain-text password, that would be great.

How do I reset the JBoss Admin password in the Developer Edition of Documentum.

(Please don't say: "Reinstall the Developer Edition")

Thanks for your help.

__________

. | homas

Find more posts tagged with

Comments

Haroon_A

1. I believe webtop is deployed on jms, please verify that, and you can restart the proper service for jms.

2. for changing your jms admin console's password, follow these steps:

To re-set/change JMS admin console's password, follow these steps:

NOTE: JMS admin console password is encrypted using the following Java class file:

com.documentum.fc.tools.RegistryPasswordUtils

1 - Encrypt the new password, using the above java class file. i.e.

$ > java com.documentum.fc.tools.RegistryPasswordUtils <jms_admin_new_password>

2 - Locate the following 2 properties files and update the value of admin's encrypted password with the new

value, obtained from step 1.

- $DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_MethodServer/conf/props/jmx-console-users.properties

- $DOCUMENTUM_SHARED /jboss4.2.0/server/DctmServer_MethodServer/deploy/management/console-mgr.sar/web-console.war/WEB-INF/classes/web-console-users.properties

3 - Save the files, and re-start JMS.

ThomasAC

Thanks for your reply. The password encryption suggestion worked fine. I'm now able to log into the JBoss control panel.

> I believe webtop is deployed on jms, please verify that, and you can restart the proper service for jms.

If by jms, you mean the Documentum Java Method Server service that I see in my Services utility, that didn't work. I have turned that service off, and JBoss and webtop are still running. I think the Documentum Java Method Server is for running methods on the content server.

I do notice a couple of .bat files in the JBOSS bin directory. I'll try a few of them to see if they work.

Any other suggestions would be apreciated, though :-)

__________

. | homas

aflowers001

Webtop etc. is installed into the Java Method Server, take a look in the ...\Documentum\jboss4.3.0\server\DctmServer_MethodServer\deploy folder and you will see this.

If they continue to run after shutting down thesefvice you will likely be hitting one of the gotchas with running Java as a service, at times it can stay running as a separate process even if the 'parent' service has shut down. I have had this with standalone JBoss as a service as well.

If shutting down the service isn't doing it for you then you may need to find the java process still running JBoss and kill that.

lastnitescurry

Install a seperate Tomcat instance and deploy your WDK app you are developing onto that. It will be far simpler and much quicker for your development

ThomasAC

> If they continue to run after shutting down the service you will

> likely be hitting one of the gotchas with running Java as a service,

> at times it can stay running as a separate process even if the

> 'parent' service has shut down. I have had this with standalone

> JBoss as a service as well.

> If shutting down the service isn't doing it for you then you may

> need to find the java process still running JBoss and kill that.

Yah, that's the ticket. After installing Sysinternals' http:Process Explorer I was able to identify and kill the java process.

> Install a separate Tomcat instance and deploy your WDK app you are

> developing onto that. It will be far simpler and much quicker for your development

I wasn't sure that you could do that with the developer edition. I'm much more familiar with Tomcat than I am with JBoss, so that would be a welcome solution. Any special things to consider if I do that?

Folks, thanks so much for the help. I really appreciate it.

DCTM_Guru

You just need to deploy your web app to tomcat. There's nothing special that binds the web app to JMS, it was just deployed there as a matter of convenience, so that you dont have to install your own app server.

You may need to change the default memory settings of your tomcat, depending on your computer for optimum performance.