xCP 1.6 Sample Application Tutorial – Mail Manager

I recently implemented the sample xCP 1.6 Mail Manager application following the tutorial, and it was an absolute pleasure going through it. There was no real problem encountered with the documentation or with the execution of the steps. The small issues that I had to deal with included some differences in the screenshots (such as Model Type field missing when creating a type in TaskSpace) and a missing step (I was expecting the step by the time I got there, so it’s easy to catch) in composing the application in TaskSpace.

I was expecting some issues as my Documentum environment is set up on Hyper-V VMs, which are not listed in the supported infrastructure. Also, I am using the 64-bit version of the Content Server.  No patches are installed though patch 6 is available at this time. My Documentum setup is summarized below:

Content Server Host

Content Server 6.7 SP1 (64-bit)
Oracle 11.2.0.2 (64-bit)
Windows 2008 R2 SP1 Enterprise (64-bit) (Hyper-V VM)

Application Server Host

Documentum applications 6.7 SP1
Tomcat 6.0.32 (64-bit)
Java 6 u33 (64-bit)
Windows 2008 R2 SP1 Enterprise (64-bit) (Hyper-V VM)

Client/Developer Desktop

Internet Explorer 9.0.9
Java 6 u33 (32-bit)
Windows 7 Ultimate Sp1 (64-bit) (Hyper-V VM)

The xCP 1.5 version of the tutorial may be found on the EMC Community Network. The xCP 1.6 version is available on Powerlink and in the download area.

While following this tutorial was easy, it took quite some patience to get all the products in the xCP bundle set up properly. For example, I installed BAM on Tomcat on the app server host and not on the Java Method Server, and that meant performing various installation steps manually. Spending time on the installation guides for all Documentum components is highly recommended.

Advertisements

Oracle Listener Problems on XP

In a development environment, I have been running Oracle 10.2.0.4 on Windows XP SP3. This database is used for a Documentum 6.5 SP2 repository. For some reason, the Oracle listener service started failing. It would stop as soon as it was started and there were no logs being generated. Starting the listener from command line would give generic errors.

I was suspecting a recent password change to be the cause. I had updated the Documentum services with the new password but the Oracle services were using the Local System account – so that wasn’t an issue. I was wondering if the password was stored somewhere and was being used internally.

After trying various things, the following two actions resumed normalcy:

  1. Turned off the firewall. The firewall has been around for a while but apparently it created some rules that were interfering with the service.
  2. I restored listener.ora and tnsnames.ora from the bak folder under network/ADMIN.

[UPDATE] I cleaned up the existing firewall rules and placed it in learning mode and that allowed Oracle and Documentum to start up fine.

Import Database from Oracle Dump

This post is probably too elementary and simplistic for anyone with Oracle administration experience. However, developers who normally don’t perform administration tasks may find it handy for setting up a DEV Oracle database.

Suppose you need to import an Oracle dump file for creating a local database copy for development purposes. The following steps can be used as a guideline.

  1. Prerequisites:
    1. Oracle database server software has been installed.
    2. An Oracle instance (say orcl) has been set up.
  2. Create a tablespace for the imported the data and associate a user with it. It can be accomplished with a script along the lines of the following. Replace the italicized tablespace name and user name/password with your own values. You can also change the database file path. Run this script when connected as SYSDBA.
    set echo on
    spool c:\temp\orcl.log
    CREATE TABLESPACE MY_TABLESPACE DATAFILE
    'C:\oracle\product\10.2.0\oradata\orcl\MY_TABLESPACE.DBF' SIZE 512M REUSE;
    ALTER DATABASE DATAFILE 'C:\oracle\product\10.2.0\oradata\orcl\MY_TABLESPACE.DBF'
    AUTOEXTEND ON NEXT 256M MAXSIZE 2048M;
    GRANT CONNECT TO myuser IDENTIFIED BY myuserpassword;
    GRANT CREATE ANY VIEW,RESOURCE,UNLIMITED TABLESPACE to
    myuser;
    ALTER USER myuser DEFAULT TABLESPACE MY_TABLESPACE
    TEMPORARY TABLESPACE TEMP;
    GRANT select_catalog_role TO myuser;
    spool off
    disconnect;
    exit;
  3. Import the dump file using the command-line utility present in the bin folder, e.g. C:\oracle\product\10.2.0\db_1\BIN. The command line would look like,
    imp myuser/myuserpassword@ORCL file=c:\temp\mydb.dmp full=yes log=c:\temp\imp.log