Archive

Posts Tagged ‘Installation’

Installing Documentum TBO using Composer

May 12, 2011 3 comments

Introduction:

The Business Object Framework (BOF) is a set of functionality that provides ability to hook into any of the methods in the standard DFC object interfaces.

BOF’s are of two kinds:

  1. Type Based Object(TBO)
  2. Service Based Object(SBO)

TBO’s are used when only one object type needs its functionality overridden whereas, we use a SBO when the functionality is overridden for different object types or in case we want to use the functionality in many other TBO’s.

The main use of TBO is the ability it gives a developer to override selected functionality of the DfSysObject or any of its child types.

Module 1: Creating the TBO

Steps to be followed for creating a TBO jar

  1. Create a java class using the same name as the object type.
  2. The java class will have to extend DfDocument and will have to override its 4 functions getVersion, getVendorString (), isCompatible (String s) and supportsFeature (String s)
  3. Then it will have to override the function that the tbo is needed for example doSave () etc.
  4. Compile this class and make a jar of it.

Module 2: Installing the TBO

Steps for installing the TBO in the docbase

  1. Create a new Documentum project in Composer
  2. Right Click on Artifacts and select New>>Other. In the New screen select Documentum Artifact>> Jar
    Definition

 

Click on Next, and in the Artifact name field enter the name of the object type and click finish

 3. Now for configuring the new jardef that we created. Since we have created only an implementation of the TBO, select Type field as Implementation. And  in the jar content browse and choose your jar file that was created in the Module 1.

4. Right Click on Artifacts and select New>>Other. In the New screen select Documentum Artifact>> Module

Click on Next, and in the Artifact name field enter the name of the object type and click finish

5. Now for configuring the new module that we created. In the Info tab select TBO from the drop down menu for Type.

6. In the Core JARs tab select Add for Implementation JARs and select the jardef created in previous step. Now click on Select in front of class Name this will display the class details of the jar in the jardef select the appropriate class.

7. Right click on Project and select the “Install Documentum Project” menu item.

Enter the username and password and click on Login button. The user will be authenticated and the Next and Finish buttons will become active. Click Finish to install the TBO into the docbase. This may take some time.

 Now whenever an object of the type for which the TBO was created is invoked or created the TBO will be fired. The TBO can be found at Cabinets>>System>>Modules>>TBO

 Module 3: Re-Installing the TBO

In case the java class has been modified, then the TBO needs to be re-installed. The steps to re-install TBO are as follows

  1. Delete the folder with the TBO name in the location (Cabinets/System/Modules/TBO)
  2. Recreate the jar using the new java file.
  3. In Composer remove the jar file from the jardef and add the new jar file
  4. Reinstall the Project to the docbase.

Prerequisites ,Installation and Configuration of ACS

November 10, 2010 Comments off

In my previous post i tried to bring out what is ACS , today lets see how we can install and configure an ACS , to start off with the Prerequisites for ACS:

a) Content Server.

b) Global registry Repository.

Installation and configuration of ACS:

Administrator doesn’t need to install it explicitly; it gets installed automatically when Content server 5.3 sp1 and above are installed. An ACS config. Object is also created automatically in the menu:

Administration-> Configuration->ACS Servers. As shown in following diagram:

 

The Administrator can check whether this service is running or not by going to following link in his system http://[system ip address]: [port no]/ACS/servlet/ACS. Or he can see the ACS service running in the services of his operating system service manager.

The Configuration of ACS means configuration of ACS server for the repository which will serve by that ACS server to specified network locations. We need to configure the ACS server config. Object for each repository, irrespective of the content server under which it is created. This configurations will be as following:

1)    Go to the Servers in Administration->configuration->Servers and click on information button to edit the properties for that server config. Object.

Go to “Connection Broker Proj” Tab and add the address of host name on which the ACS server is installed and also specify the Proximity for that Server. Administrator can add more than one connection broker to one repository at any time.

Now after following the above steps , you will see that the ACS server got added to server config object:

2)    Go to the “Network Location Proj “ tab to add the network location to be served by the repository.

Network Location got added to Server Config Object as in below:

3)    Now save and come out of the server config object to the ACS server config Object. And verify the “Connection Broker Projection” and “Network Location projection” for correct entries.

Now the ACS server is configured to the Repository server through a Connection broker to serve a set of network location.

Note: While creating the connection broker object take care for false host name because the Documentum never verifies for fake/non existing hosts.

DFC Installation and Configuration

April 16, 2010 Comments off

The below steps will guide  you to install & Configure  DFC :

Step 1: Use dfcWinSuiteSetup.exe to start the DFC installation.

Step 2: A welcome dialog box appears, click next to proceed to the next window.

Step 3: The license agreement is displayed, select the accept option and click next.

Step 4: Mention the path where you need to install DFC programs and click next.

Step 5: Specify whether to install optional components for developers like developer documentation and Primary Interop Assembly Installer.

Step 6: Specify the root directory for documentum user information and click next.

Step 7: Specify the host and port number for the connection broker machine.

Step 8: Check the global registry checkbox to use DFC as global registry.

Step 9: See the progress and click finish when the installation reports that it has successfully installed DFC.

The Following Files are required to run DFC and BOF programs. You can find the files in Directory “<<drive>>”:\Documentum\config

  1. dfc.properties
  2. dfcfull.properties
  3. dbor.properties
  4. log4j.properties

dfc.properties

Set preferences for how DFC handles certain choices in the course of its execution.

dfcfull.properties

This file contains documentation of all recognized properties and their default settings. (Do not modify this file and copy the properties to dfc.properties file)

Another important property is set dfc.registry.mode = file. This causes DFC to use a file to store certain settings, rather than the Windows registry. This is the standard setting for UNIX systems. It also works for Windows systems, but that setting is incompatible with Documentum Desktop.

dbor.properties

Contains registry entries for BOF classes.

log4j.properties

Configuring Log Properties

Edit dmcl.ini found in C:\WINNT

[DOCBROKER_PRIMARY]

Host: Docbroker IP

Port: Port which Docbroker is listening

%d bloggers like this: