Migration to exchange 2007

Exchange Server 2007 does not support in-place upgrades,because exchange 2007 in production environment run only on 64Bit hardware.
Exchange Server 2003 will run on 64-bit hardware, but only if it is running a 32-bit operating system. This difference in required operating systems makes an in-place upgrade impossible

you have to migrate by getting new hardware for exchange 2007,and install exchange in current domain or in current forest.then you have to migrate mailboxes from exchange 2003 by using command shell or by using management console.
64-bit operating systems have a much larger memory address space than their 32-bit counterparts, and that this larger address space facilitates the creation of larger Exchange databases. Exchange Server 2003 Enterprise Edition did not impose a database size limit, but there was a practical limit to the size to which a database could grow that was based on hardware constraints. These constraints have all but vanished from Exchange in Exchange

Server 2007, allowing you the freedom to create some truly massive databases.
The biggest thing to keep in mind is that Exchange Server 2007 modifies the Active Directory schema during installation. Therefore, I recommend making a full system backup of your domain controllers prior to installing Exchange.

Now install exchange server 2007 according to the requirement,typical or custom.
when installation completes,it time to migrate the mailboxes from exchange 2003 to exchange 2007.

- convert exchange 2003 to native mode.

Migrating mailboxes is simple: go to your Exchange 2007 server and open the Exchange Management Console. When the console opens, navigate through the console tree to Recipient Configuration Mailbox.When you click on Mailbox, the console's detail pane will display a list of mailbox in the entire Exchange Server organization,right click one or more mailbox and click "Move"

Installation of IBM FileNet CE 4.0:

FileNet Contant Engine can be installed with anyone of the databases like SQL Server,Oracle and DB2.
One application server is also required for CE installation. you can use one of the Application Server with CE from
- Bea Weblogic 8.1.6 or 9.0
- JBoss Application Server 4.0.5(Only one version with support CE 4.0)
- Websphere 6.0/6.1
Installation of CE with Bea Weblogic and SQL Server 2000
- install Bea weblogic server version mentioned above.
- install SQL server 2000 with SP3 /SP4
- Copy latest JDBC driver for SQL- Add "weblogic.jar" file path to class path
- copy "sqljdbc.jar" from JDBC driver directory to SQl server and Weblogic "Bin" directory.
- copy "xa_install.sql" and "sqljdbc_xa.dll" to SQL server Binn directory.
- Run "xa_install.sql" script by selecting "MASTER" database.
- Restart the Weblogic Application Server.
- In the weblogic console create two connection pool for CE,by selecting Bea driver.
- Create DSN using above pool.
- Install CE 4.0.

IBM FileNet Business Process Framework 4.1

For BPF installation ,you need:--
A fully functional IBM FileNet Environment having PE,CE,and AE configured.
- Workplace is Working
- Create 3 or 4 user in AD
- Create 5 roles is Workplace and assign different user to different role.
- download jtds driver "jtds-1.2.2-dist.zip" from http://www.sourceforge.net/ and install it
- copy "JtdsXA.dll " and jtds-1.2.2.jar from the driver directory to the BINN folder in Bea andSQL server installation directory.
- run Script ''instjtds.sql" inside the driver directory by selecting "master database".
- Start setup by clicking "WINDOWSfilenet_bpf_setup.exe" when asked JDBC driver locationenter"C:\bea\weblogic81\server\lib"After installation completes,
Install BPF Explorer available inside the BPF source directory.
- Define Role in BPF explorer also.
ISSUES:
if you have more than one Object Store in CE,and BPF preferences object Store is different form Workplace Preferences object Store ,then you have problem in opening the BPF application homepage.You have to save BPF preference and Workplace preference in same object store.