nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Still only 1 Java MS after installing a 2nd content server?

Mbacct

Hi!

I added a second content server (running on a seperate machine) to my environment. I installed it by choosing "Configure Content-File Server for use with an existing repository" in the server setup. Everything went fine and both content servers seem to work hand-in-hand

However while browsing through the DA I noticed that there is only 1 Java Method Server listed in "Administration > Basic Configuration > Java Method Servers" (i.e. the JMS of content server #1). Is that ok? Shouldnt it be two, one for each content server?

The other settings in the DA all list 2 elements - for example "Administration > Basic Configuration > Content Servers" shows both content servers, as well as "Administration > Distributed Content Configuration > ACS Servers" also shows 1 entry for each content server.

Why is there only 1 method server? Should I add the missing one?

Best regards,

Find more posts tagged with

Comments

Julien.Fontaine

What's your need, do you want to have one or two JMS instances ?

Both configuration are possible.

Mbacct

I installed the second content server for high availability reasons. So I guess I want to have 1 JMS for each content server? But why hasnt it been added by the setup? Did something go wrong?

Julien.Fontaine

If you use DCTM 6.6 higher, you can achieve your requirement. Go to the Installation Guide, you have a special part for this (e.g : for example Installing and configuring JMS for HA on a single host).

Good luck.

kcrkarthik

In the properties of the server config objects, are both the object pointing to the same JMS or each pointing to its own JMS?

Check in the App Servers tab of the server config object.

Are you able to designate a job to the 2nd server and run that? may be it is just that, the JMS config object is not created.

-karthik

Julien.Fontaine

You CAN also check if you have a Jboss folder on your second content server located in $documentum_home.

Mbacct

Thanks guys! Great help!

Alright, here we go:

@Karthik: In the App Servers tab, each content server points to its own JMS (at least that's what the URI of do_method and do_mail says).

And I was able to run dm_ConsistencyChecker on CS#2, so I guess it works.

@Julien: Yes, I have a jboss located at $documentum_hom\jboss4.3.0

Since everything seems to work fine - should I simply add the second JMS manually? I was just wondering whether this hasnt been done by the setup already...

kcrkarthik

I don't have an environment to check that. may be the CFS installer doesn't create it. But still, what is the significance of that object when things are working fine?

You can try creating one manually. I don't think it would affect any.

-karthik

Julien.Fontaine

Please dump your dm_server_config for each server.

Mbacct

Yeah I was just wondering.... I tried to understand what happens when I add a second content server. My assumption was, that there should be a second entry for the second JMS. But you're right, as far as everything works fine....

However especially when it comes to setting up a failover solution you cannot be 100% sure that everything will still work after x services have failed. Maybe there is a scenario which requires that second entry.

@dump: working on that. I'll get back to you asap

Julien.Fontaine

Ok... Wait for your dumps !

Mbacct

Ok, please find attached the dumps of the two dm_server_configs. Note that for company policy reasons I had to change the machine names and IDs. But I guess that's not important anyways.

Object 1

USER ATTRIBUTES

object_name : MyDocbaseID

title :

subject :

authors []: <none>

keywords []: <none>

resolution_label :

owner_name : MyDocbaseID

owner_permit : 7

group_name : docu

group_permit : 5

world_permit : 3

log_entry :

acl_domain : MyDocbaseID

acl_name : dm_4501234560000100

language_code :

concurrent_sessions : 100

server_cache_size : 200

client_cache_size : 50

nfs_enabled : F

secure_writer_location :

user_validation_location :

compound_integrity : T

system_converter_location : convert

stage_destroyer_location :

cached_types []: <none>

far_stores []: <none>

user_converter_location :

netstor_bin_location :

log_location : log

common_location : common

temp_location : temp

nls_location : nls_chartrans

locale_name : de

checkpoint_interval : 300

keep_entry_interval : 1440

sibling_checkpoint_interval : 300

sibling_export_enabled : T

operator_name : MyDocbaseID

assume_user_location : assume_user

change_password_location : change_password

turbo_backing_store : filestore_01

events_location : events

agent_launcher : agent_exec_method

default_acl : 1

verity_location : DoNotUse

rend_backing_store : filestore_01

projection_targets [0]: MYCONT02

projection_ports [0]: 1489

projection_proxval [0]: 2

projection_notes [0]: Projecting primary to remote.

projection_enable [0]: T

signature_chk_loc : check_signature

alias_set_id : 0000000000000000

web_server_loc : MYCONT01

rightsite_image :

web_server_port : 80

ldap_config_id : 0000000000000000

login_ticket_timeout : 5

default_client_codepage : ISO_8859-1

server_os_codepage : ISO_8859-1

app_server_name [0]: do_method

[1]: do_mail

[2]: MYINDEXSRV01_9200_IndexAgent

[3]: MYINDEXSRV02_9200_IndexAgent

[4]: adobe_comment_connector

app_server_uri [0]: http://MYCONT01:9080/DmMethods/servlet

oMethod

[1]: http://MYCONT01:9080/DmMail/servlet/Do

[2]: http://MYINDEXSRV01:9200/IndexAgent/servle

IndexAgent

[3]: http://MYINDEXSRV02:9200/IndexAgent/servle

IndexAgent

[4]: http://192.168.0.31:80

smtp_server : MYSMTPSRV

secure_connect_mode : native

auth_plugin_location : auth_plugin

dba_location : dm_dba

wf_agent_worker_threads : 3

wf_sleep_interval : 5

mail_method :

application_access_control : F

max_login_ticket_timeout : 43200

restrict_su_ticket_login : F

extra_directory_config_id []: <none>

fulltext_location : dsearch

projection_netloc_enable [0]: F

projection_netloc_id [0]:

max_cm_parallel_degree : 10

system_shutdown_timeout : 120

wf_agent_notify_newtask : T

SYSTEM ATTRIBUTES

r_object_type : dm_server_config

r_creation_date : 24.04.2012 14:33:16

r_modify_date : 15.05.2012 13:26:38

r_modifier : MyDocbaseID

r_access_date : nulldate

r_composite_id []: <none>

r_composite_label []: <none>

r_component_label []: <none>

r_order_no []: <none>

r_link_cnt : 0

r_link_high_cnt : 0

r_assembled_from_id : 0000000000000000

r_frzn_assembly_cnt : 0

r_has_frzn_assembly : F

r_is_virtual_doc : 0

r_page_cnt : 0

r_content_size : 0

r_lock_owner :

r_lock_date : nulldate

r_lock_machine :

r_version_label [0]: 1.0

[1]: CURRENT

r_immutable_flag : F

r_frozen_flag : F

r_has_events : F

r_creator_name : MyDocbaseID

r_is_public : T

r_policy_id : 0000000000000000

r_resume_state : 0

r_current_state : 0

r_alias_set_id : 0000000000000000

r_full_content_size : 0

r_aspect_name []: <none>

r_server_version : 6.7.0020.0225 Win64.SQLServer

r_host_name : MYCONT01

r_process_id : 3884

r_install_owner : myuser

r_install_domain : mycompany

r_trusted_mode : 0

r_castore_enabled : 0

r_object_id : 3d01234560000102

APPLICATION ATTRIBUTES

a_application_type :

a_status :

a_is_hidden : F

a_retention_date : nulldate

a_archive : F

a_compound_architecture :

a_link_resolved : F

a_content_type :

a_full_text : T

a_storage_type :

a_special_app :

a_effective_date []: <none>

a_expiration_date []: <none>

a_publish_formats []: <none>

a_effective_label []: <none>

a_effective_flag []: <none>

a_category :

a_is_template : F

a_controlling_app :

a_extended_properties []: <none>

a_is_signed : F

a_last_review_date : nulldate

a_silent_login : T

INTERNAL ATTRIBUTES

i_is_deleted : F

i_reference_cnt : 1

i_has_folder : T

i_folder_id [0]: 0c01234560000106

i_contents_id : 0000000000000000

i_cabinet_id : 0c01234560000106

i_antecedent_id : 0000000000000000

i_chronicle_id : 3d01234560000102

i_latest_flag : T

i_branch_cnt : 0

i_direct_dsc : F

i_is_reference : F

i_retain_until : nulldate

i_retainer_id []: <none>

i_partition : 0

i_is_replica : F

i_vstamp : 37

Object 2

USER ATTRIBUTES

object_name : mydocba_MyDocbaseID_Cont02

title :

subject :

authors []: <none>

keywords []: <none>

resolution_label :

owner_name : myuser

owner_permit : 7

group_name : docu

group_permit : 5

world_permit : 3

log_entry :

acl_domain : MyDocbaseID

acl_name : dm_4501234560000100

language_code :

concurrent_sessions : 100

server_cache_size : 200

client_cache_size : 50

nfs_enabled : F

secure_writer_location :

user_validation_location :

compound_integrity : T

system_converter_location : convert

stage_destroyer_location :

cached_types []: <none>

far_stores []: <none>

user_converter_location :

netstor_bin_location :

log_location : log

common_location : common

temp_location : temp

nls_location : nls_chartrans

locale_name : en

checkpoint_interval : 30

keep_entry_interval : 1440

sibling_checkpoint_interval : 300

sibling_export_enabled : T

operator_name : MyDocbaseID

assume_user_location : assume_user

change_password_location : change_password

turbo_backing_store : filestore_01

events_location : events

agent_launcher : agent_exec_method

default_acl : 1

verity_location : DoNotUse

rend_backing_store : filestore_01

projection_targets [0]: MYCONT02

projection_ports [0]: 1489

projection_proxval [0]: 9010

projection_notes [0]: From server.ini

projection_enable [0]: T

signature_chk_loc : check_signature

alias_set_id : 0000000000000000

web_server_loc : MYCONT02

rightsite_image :

web_server_port : 80

ldap_config_id : 0000000000000000

login_ticket_timeout : 5

default_client_codepage : ISO_8859-1

server_os_codepage : ISO_8859-1

app_server_name [0]: MYINDEXSRV01_9200_IndexAgent

[1]: MYINDEXSRV02_9200_IndexAgent

[2]: do_method

[3]: do_mail

[4]: adobe_comment_connector

app_server_uri [0]: http://MYINDEXSRV01:9200/IndexAgent/servlet/

IndexAgent

[1]: http://MYINDEXSRV02:9200/IndexAgent/servlet/

IndexAgent

[2]: http://MYCONT02:9080/DmMethods/servlet/D

oMethod

[3]: http://MYCONT02:9080/DmMail/servlet/DoMa

[4]: http://192.168.0.31:80

smtp_server :

secure_connect_mode : native

auth_plugin_location : auth_plugin

dba_location : dm_dba

wf_agent_worker_threads : 3

wf_sleep_interval : 5

mail_method :

application_access_control : F

max_login_ticket_timeout : 43200

restrict_su_ticket_login : F

extra_directory_config_id []: <none>

fulltext_location : dsearch

projection_netloc_enable [0]: F

projection_netloc_id [0]:

max_cm_parallel_degree : 10

system_shutdown_timeout : 120

wf_agent_notify_newtask : T

SYSTEM ATTRIBUTES

r_object_type : dm_server_config

r_creation_date : 27.04.2012 10:22:11

r_modify_date : 15.05.2012 13:16:58

r_modifier : MyDocbaseID

r_access_date : nulldate

r_composite_id []: <none>

r_composite_label []: <none>

r_component_label []: <none>

r_order_no []: <none>

r_link_cnt : 0

r_link_high_cnt : 0

r_assembled_from_id : 0000000000000000

r_frzn_assembly_cnt : 0

r_has_frzn_assembly : F

r_is_virtual_doc : 0

r_page_cnt : 0

r_content_size : 0

r_lock_owner :

r_lock_date : nulldate

r_lock_machine :

r_version_label [0]: 1.0

[1]: CURRENT

r_immutable_flag : F

r_frozen_flag : F

r_has_events : F

r_creator_name : myuser

r_is_public : T

r_policy_id : 0000000000000000

r_resume_state : 0

r_current_state : 0

r_alias_set_id : 0000000000000000

r_full_content_size : 0

r_aspect_name []: <none>

r_server_version : 6.7.0020.0225 Win64.SQLServer

r_host_name : MYCONT02

r_process_id : 0

r_install_owner : myuser

r_install_domain : mycompany

r_trusted_mode : 0

r_castore_enabled : 0

r_object_id : 3d01234560003551

APPLICATION ATTRIBUTES

a_application_type :

a_status :

a_is_hidden : F

a_retention_date : nulldate

a_archive : F

a_compound_architecture :

a_link_resolved : F

a_content_type :

a_full_text : T

a_storage_type :

a_special_app :

a_effective_date []: <none>

a_expiration_date []: <none>

a_publish_formats []: <none>

a_effective_label []: <none>

a_effective_flag []: <none>

a_category :

a_is_template : F

a_controlling_app :

a_extended_properties []: <none>

a_is_signed : F

a_last_review_date : nulldate

a_silent_login : T

INTERNAL ATTRIBUTES

i_is_deleted : F

i_reference_cnt : 1

i_has_folder : T

i_folder_id [0]: 0c01234560000106

i_contents_id : 0000000000000000

i_cabinet_id : 0c01234560000106

i_antecedent_id : 0000000000000000

i_chronicle_id : 3d01234560003551

i_latest_flag : T

i_branch_cnt : 0

i_direct_dsc : F

i_is_reference : F

i_retain_until : nulldate

i_retainer_id []: <none>

i_partition : 0

i_is_replica : F

i_vstamp : 24

Julien.Fontaine

Everything sounds good in your dump. I think it must work by now !

Mbacct

Alright, great! Thanks!

On a related note: I just found out that I also only got 1 Connection Broker registered for each content server (DA > Basic Configuration > Content Servers > [pick server] > Properties > Connection Brokers). The funny thing is, that:

* For CS#1 the Connection Broker is the one of CS#2 with the note "Projecting primary to remote"

* For CS#2 the Connection Broker is ALSO the one of CS#2, but with the note "from server.ini"

The failover if one CB is shut down seems to work thoug....So I guess that's fine, too?

Julien.Fontaine

Alright, that's Good news.

Please mark your question as answered of everything it's now ok !

Mbacct

So far, yes. But what's your opinion on the connection broker issue (see my last posting)?

Julien.Fontaine

You can project to one or two docbroker. In a full failover perspective, you must project to two docbroker, if you want to avoid failure on one content server.

Mbacct

Sorry for the late response.

Alright, so I will add the second docbroker. But again, I am wondering why this hasnt been done by the setup....

Julien.Fontaine

Cause it's not the only coonfiguration possible. For example, you can have one CS for user purposes and another one for JMS purposes. In this case, you don't need two docbroker, etc ....

Don't forget to mark your question as answered, it's more easy for search !

Mbacct

Sure, will do

One last thing: I also entered the [DOCBROKER_PROJECTION_TARGET_1]-block in the server.ini's of both content servers (of course in each .ini the address of the other content server). Will this setting override the settings of the Documentum Administrator (I mean the one at DA > Basic Configuration > Content Servers > [pick server] > Properties > Connection Brokers)? Do I still need to enter both docbrokers for both content servers in the DA or is it sufficient to have them in the corresponding server.ini's?

Julien.Fontaine

The server.ini must be enough. You can try by stopping one Docbroker !

Mbacct

Yes, it does work.

However my setup* was completely different to the one described in the manual (EMC Documentum Content Server Enterprise Edition Version 6.7 Installation Guide, page 130) and I still have only 1 dm_jms_config object.

I am wondering whether this has any negative effects regarding HA or load balancing between the two content servers....?

____

* After installing the second content server, I simply added the [DOCBROKER_PROJECTION_TARGET_1]-block to the server.ini of the first content server (because it was already added to the server.ini of the second CS). The manual says that there should be a second dm_jms_config object that I need to configure.