What is global registry and how to know a repository is a global registry

What is global registry and how to know a repository is a global registry

http://markmail.org/message/2lyv4r4lmjwoodxm

 

Starting in 6.0 every installation must have a Docbase designated as a global registry even if you only plan to have the one Docbase and even if you're not using distributed Content Servers. Specifying a Docbase as a global registry is optional during Content Server installation but a global registry must be configured before connecting to the Docbase with any client applications.

To use BOF (TBO/SBO) requires that at least one of your Repositories be designated as the BOF Global Registry. Each Application Server must identify the BOF Global Registry it will use via the dfc.properties file.

There are two parts to setting up the BOF Global Registry:

1) making sure the "dm_bof_registry" Repository user is active.

2) making sure that the dfc.properties file on your Application Server(s) are correctly referencing the Repository that is acting as the BOF Global Registry and has the listed the correct user information for the dm_bof_registry user.

1. Verifying that a Repository is the BOF Global Registry:

===================================

-Using Documentum Administrator (DA), log into the Repository that should be the BOF Global Registry, using an administrator account.

-In Classic view, in the left navigation tree, click on the Administration node. In the page that appears, under the heading "User Management", click on "Search for Users".

-Search for the following user: 'dm_bof_registry" (enter this value next to the User Name label, and click Search).

-View the properties of this user "dm_bof_registry" (click the (i) icon).

-Make note of the user's 'State' and 'User Login Name'.

If the user State is 'Inactive', then this Repository is not the BOF Global Registry. To make this Repository the BOF Global Registry, follow Steps 2-4.

If the BOF Global Registry user is 'Active', you need to verify some information in your dfc.properties file on your Application Server (s).

From the Application Server machine, locate the dfc.properties file.

Open this file in any text editor. Ensure the following three attributes are set in the dfc.properties file:

dfc.bof.registry.repository =

dfc.bof.registry.username =

dfc.bof.registry.password =

Without the above three entries, the BOF Global Registry will not be set.

If these entries are missing or values are not complete, you will need to add and populate these values. See the following steps for more details.

2. Enabling the BOF Global Registry

===================================

The following section outlines the steps required to enable the BOF Global Registry using the Documentum Administrator (DA) application.

-Log into Documentum Administrator (DA) as an Administrator in the Repository where you want to enable TBO/SBO functionality.

-In Classic view, in the tree, click on the Administration node. In the page that appears, under the heading "User Management", click on "Search for Users".

-Search for the following user: 'dm_bof_registry" (enter this value next to the User Name label, and click Search).

-View the properties of this user 'dm_bof_registry" (click the (i) icon).

- The properties page will appear. From the properties page, ensure the following options and values are set to the following:

User State: Active

User Source: Inline Password

Restrict Folder Access: System

- For security purposes, change the default password (make a note of the new password).

- Click OK on the 'dm_bof_registry' user 'Properties' page.

3. Verifying the dfc.properties file

====================================

On each Application Server, locate the dfc.properties file. Open this file in any text editor. Ensure the following three attributes are set in the dfc.properties file:

dfc.bof.registry.repository =

dfc.bof.registry.username =

dfc.bof.registry.password =

Without the above three entries, the BOF Global Registry will not be set.

Note: The password supplied in the entry 'dfc.bof.registry.password' must be consistent with the password provided when setting the 'dm_bof_registry' password via Documentum Administrator (DA). The password must also be encrypted. For information on how to encrypt the password, see the next section in this document, entitled 'Encrypting Passwords for the dfc.properties file'.

4. Encrypting Passwords for the dfc.properties file

===================================================

The password provided in the 'dfc.properties' file must be encrypted. A utility is provided to encrypt this password. The following section outlines the steps required to invoke the password utility program to encrypt a password.

From a command prompt, execute the following:

java com.documentum.fc.tools.RegistryPasswordUtils <password>

Note- If you are using java methods that use the TBOs/SBOs then you will need the following entries on the % DM_Home/config/dfc.properties file as well

dfc.bof.registry.repository =

dfc.bof.registry.username =

dfc.bof.registry.password =

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
提供的源码资源涵盖了小程序应用等多个领域,每个领域都包含了丰富的实例和项目。这些源码都是基于各自平台的最新技术和标准编写,确保了在对应环境下能够无缝运行。同时,源码中配备了详细的注释和文档,帮助用户快速理解代码结构和实现逻辑。 适用人群: 适合毕业设计、课程设计作业。这些源码资源特别适合大学生群体。无论你是计算机相关专业的学生,还是对其他领域编程感兴趣的学生,这些资源都能为你提供宝贵的学习和实践机会。通过学习和运行这些源码,你可以掌握各平台开发的基础知识,提升编程能力和项目实战经验。 使用场景及目标: 在学习阶段,你可以利用这些源码资源进行课程实践、课外项目或毕业设计。通过分析和运行源码,你将深入了解各平台开发的技术细节和最佳实践,逐步培养起自己的项目开发和问题解决能力。此外,在求职或创业过程中,具备跨平台开发能力的大学生将更具竞争力。 其他说明: 为了确保源码资源的可运行性和易用性,特别注意了以下几点:首先,每份源码都提供了详细的运行环境和依赖说明,确保用户能够轻松搭建起开发环境;其次,源码中的注释和文档都非常完善,方便用户快速上手和理解代码;最后,我会定期更新这些源码资源,以适应各平台技术的最新发展和市场需求。 所有源码均经过严格测试,可以直接运行,可以放心下载使用。有任何使用问题欢迎随时与博主沟通,第一时间进行解答!

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值