Creating a new Object Store in FileNet 5.1

//Creating a new Object Store in FileNet 5.1

3 main steps required for creating a new object store

1. Create a new Data Base
2. Create XA and Non-XA Data Sources in WebSphere
3. Create a new Object Store using FileNet Enterprise Manager Administration Tool 

1. Create a new Data Base (Here i am creating a database in SQL Server)

2. Create XA and Non-XA Data Sources in WebSphere

(Non-XA Data Source)
2.1 Log-on to WebSphere console and navigate to Data Sources as shown below and Click on New

  


2.2 Enter Data source name and JNDI name and click on Next

2.3 Select Non-XA data source as shown below and click on NEXT 

2.4 Enter Database Name, Port number, Server Name and Click on Next

2.5 Select "Component-managed Authentication alias" (for Authentication) and click on Next and Finish it.
2.6 Test the connection.

(XA Data Source)

 2.7 Log-on to WebSphere console and navigate to Data Sources as shown below and Click on New
 
 
2.8 Enter Data source name and JNDI name and click on Next

2.9 Select XA data source as shown below and click on NEXT

2.10 Select "Component-managed Authentication alias" (for Authentication) and click on Next and Finish it.

   
2.11 Test the two (XA and Non XA Data Sources).

3. Create a new Object Store using FileNet Enterprise Manager Administration Tool  

3.1 Log on to FileNet Enterprise Manager Administration Tool (FEM)

3.2 Right click on Object Stores and click on New Object Store

3.3 Click on Next

3.4 Enter Display Name*, Symbolic Name* and Description and click on Next

 3.5 Enter JNDI Data Source Name, JNDI XA Data Source Name (Same as you created in 2 Step) and Click on Next

3.5  Create a new empty folder in Windows (or Linux)(For File Storage Area) (Here Folder Name : RAKESHOS)

 
3.6 Select File Storage Area and click on Next.

3.7 Browse... the Root Directory of Folder  (Here I am selecting RAKESHOS folder) and Click on Next

 

 3.8 Enter Storage Area Details as shown below and Click on Next

3.9 Add user(s) or (and) groups that should have administrative access to the object store and Click on Next

 

 3.10 Add user(s) or (and) groups that should have basic, non-administrative access to the object store

3.11 Select AddOns to install(Minimal AddOns mandatory) and Click on Next. Select the AddOns based on your requirement (for example Case Manager Target object store or Design object store or (and) Workplace/XT AddOns)  (Hare i am selecting Workplace/XT and Case Manager Target Object store related AddOns) .

3.12 Finish the changes and it will take some time to create a Object Store.

 

 ....Object Store created successfully...

****************************************************************************************

Java code to Create/Delete user in LDAP

//Java code to Create/Delete user in LDAP

// Establish a LDAP connection

public static LdapContext getInitialLdapContext()
        throws Exception
    {
        LdapContext ctx = null;
        String dnusername = "cn=root,ou=users, o=sample,c=country"; //Admin user name
        String dnpwd = "abcd@123"; //Admin Password
        try
        {
            Control rctls[] = {new PasswordPolicyControl(true)};
            String ldapHostName = bundle.getString("LDAP_IP");
            String ldapHostRMIPort = bundle.getString("LDAP_PORT");
            String providerURL = (new StringBuilder("ldap://")).append(ldapHostName).append(":").append(ldapHostRMIPort).toString();
            System.out.println("URL  =  "+ providerURL);
            Hashtable env = new Hashtable();
            env.put("java.naming.factory.initial", "com.sun.jndi.ldap.LdapCtxFactory");
            env.put("java.naming.provider.url", providerURL);
            env.put("java.naming.security.authentication", "simple");
            env.put("java.naming.security.principal", dnusername);
            env.put("java.naming.security.credentials", dnpwd);
            ctx = new InitialLdapContext(env, rctls);
        }
        catch(Exception e)
        {
            e.printStackTrace();
        }
        return ctx;
    }
    private static String getUserDN(String username)
    {
        return (new StringBuilder("cn=")).append(username).append(",").append("ou=users, o=sample,c=country").toString();
    }
   
   
    //Create a user
   private static void addUser(String username, String surname,  String titleprop, String mailprop, String employeenumberprop, String mobileprop, String displayNameprop, String password)
       // throws NamingException
    {
        private static DirContext context;
        context = getInitialLdapContext();
        Attributes container = new BasicAttributes();
        Attribute objClasses = new BasicAttribute("objectClass");
        objClasses.add("organizationalPerson");
        objClasses.add("inetOrgPerson");
        objClasses.add("person");
        objClasses.add("top");
        Attribute cn = new BasicAttribute("cn", username);
        Attribute sn = new BasicAttribute("sn", surname);
        Attribute uid = new BasicAttribute("uid", username);
        Attribute title = new BasicAttribute("title", titleprop);
        Attribute mail = new BasicAttribute("mail", mailprop);
        Attribute mobile = new BasicAttribute("mobile", mobileprop);
        Attribute employeeNumber = new BasicAttribute("employeeNumber", employeenumberprop);
        Attribute userPassword = new BasicAttribute("userpassword", password);
        Attribute  displayName = new BasicAttribute("displayName",displayNameprop);
        container.put(objClasses);
        container.put(sn);
        container.put(uid);
        container.put(title);
        container.put(mail);
        container.put(mobile);
        container.put(employeeNumber);
        container.put(countryCode);
        container.put(displayName);

        container.put(userPassword);
       try{
        context.createSubcontext(getUserDN(username), container);
       }
       catch (Exception e) {
        // TODO: handle exception
           log.info(e);
    }
       
       System.out.println((new StringBuilder(String.valueOf(password))).append("- is the Password for user- ").append(username).toString());
       
    }
   
    //Delete a user
    private static void deleteUser(String username)
        throws NamingException
    {
        try
        {
            context.destroySubcontext(getUserDN(username));
            System.out.println((new StringBuilder("User has been deleted successfully - ")).append(username).toString());
        }
        catch(NameNotFoundException namenotfoundexception) {
            log.info(namenotfoundexception);
        }
    }
   

   

Connection Points and Isolated Regions

//Connection Points and Isolated regions


Connection Points: Connection points replace the router process used in previous Process Engine releases, connecting the Process Engine API to an associated isolated region. Connection points are defined in the Content Engine API (the PEConnectionPoint and IsolatedRegion classes) and persisted in the Global Configuration Data (GCD) on the Content Engine. Multiple connection points can reference the same isolated region. The set of connection points defined is reflected in the Content Engine's Domain.PEConnectionPoints property. To create and manage connection points, use the IBM Administration Console for Content Platform Engine.

To establish or log on to a Process Engine session a connection point must be specified and the Content Engine host must be accessible.

Isolated regions: An isolated region is a logical subdivision of the workflow system. Isolated regions are often used to separate development, testing, and production environments such that developers and testers can share computing resources while still keeping their disparate activities isolated. An isolated region consists of queues, rosters, and event logs.

An isolated region is identified by one or more connection points. Information that is common to all regions in the workflow system is contained in the workflow system properties.

You can initialize or delete an isolated region. In addition, you can delete the workflow system. Typically, these activities are performed only in a development environment.

FileNet Architecture

//FileNet Architecture

High Level View: 

 

This is not intended to be a logical architecture view in the true sense. Taking a look at this from the top  down you will find that this is a user interface (Web Clients), web application server (Presentation Layer), major engines (Services Layer) with connectivity to the repository (Data Layer).

Web Clients layers is a brief view into commonly used end user interfaces into the P8 architecture.

Presentation Layer is a look into the applications built on P8 architecture offered by FileNet. One key note here is the Workplace and eForms are highlighted here even though they are not packaged applications in and of themselves. The business logic layer speaks to just that the application logic that is used by the various packaged FileNet applications.

Services Layer is a look into the main 3 engines with a connotation of the connectivity that exists into the back end repositories.

Data Layer speaks to the various forms or types of storage devices/mediums that are compatible with the architecture.Data Layer shows general categories of P8 content storage (File System, Database) and specific devices that are supported in those categories. For example, rewritable magnetic disk for Database; rewritable magnetic disk for File System,  WORM magnetic disk for (Fixed) File System, optical and tape (various methods).

Things that are notably left out are for example: LDAP, API, XML Web Services, etc. These are seen the subsequent more granular views.

--------------------------------------------------------------------------------------------------------------------------------------------------

Mid Level View:

In this view, the architecture is broken down into four areas: Presentation, Business Logic, Services, Data, and Clients.

Web Clients: The web clients box is to show the common end user applications or interfaces into the P8 architecture. They can been seen in three buckets: browser based, office/application integration, and WebDAV based. These commonly interact with the presentation layer via the APIs into the Services layer engines.

Presentation Layer: The presentation layer is a look into what runs in the web application server (BEA, IBM, etc.). These here are grouped into a common suite format such as: CM, BPM, WCM, TCM and RM. There is also a further look into specific functionality such as Workplace, eForms, Content Provider and an IS Servlet. Each of these interfaces or groupings in this layer are intended to show the higher level functionality offered businesses from a functional grouping perspective.

Business Logic Layer: The business logic layer here is intended to show just that the business logic of the applications or suites from the Presentation Layer. Here what is shown is both the COM and Java APIs into the Services Layer engines. There is also a view into the Image Services Resource Adapter (ISRA) that is a JCA connector that interfaces into Image Services.

Services Layer: The services layer is where the three main engines are shown: Content Engine, Process Engine, and Image Services. The other main thing in this layer is the XML Web Services that are shown connecting or allowing an interface into both the Process and Content Engines via the Web Services Interface. For completeness, there is also a box to show the connectivity or EAI connection into other various business applications. There is also a box to depict the process optimization (Process Analyzer, Process Simulator, and Rules Engine) portions of the BPM offering.

Client Applications: There is a box of clients directly connecting into the Services Layer. This is shown here due to the administrative nature of these applications such as the Enterprise Manager that connects into the Content Engine. Keep in mind that this is not a complete logical architecture diagram since it is still high level in its depicting the architecture.

Data Layer: The data layer shows the various repository options for both the CE and IS. It also shows the ability to connect to various existing business/legacy applications. There is also a depiction indicating the connectivity or use of an LDAP server for authentication and authorization since P8 does no identity management.

Magnetic Disk includes both rewritable magnetic disk (NAS, SAN, iSCSI) and WORM magnetic disk (NetApp SnapLock, EMC Centera, etc.) offerings.

-------------------------------------------------------------------------------------------------------------------------------------------------

Low Level View:

 

The low level view is intended for a much more technical audience those that will do architectural designs or implementation of the FileNet solution. This is on the logical architecture level.

Web Clients: The web clients box is to show the common end user applications or interfaces into the P8 architecture. They can been seen in three buckets: browser based, office/application integration, and WebDAV based. These commonly interact with the presentation layer via the APIs into the Services layer engines.

Presentation Layer: The presentation layer is a look into what runs in the web application server (BEA, IBM, etc.). These here are grouped into a common suite format such as: CM, BPM, WCM, TCM and RM. There is also a further look into specific functionality such as Workplace, eForms, Content Provider and an IS Servlet. Each of these interfaces or groupings in this layer are intended to show the higher level functionality offered businesses from a functional grouping perspective. There is a clear line connecting to the business logic where applications have a higher level of business logic built on top of the existing APIs.

Business Logic Layer: The business logic layer here is intended to show just that the business logic of the applications or suites from the Presentation Layer. Here is where a higher level of functionality or business logic is shown above the Java and COM APIs. This is depicted in the Services boxes such as Collaboration Services for example. This is where the lower level Java API functionality is taken to a higher level abstraction with a logical business or application grouping of functionality.

In this layer there is also a depiction of the Component Integrator which is part of the functionality offered in the Process Engine and packaged as part of the BPM suite.

There is also a box showing the BEA Content SPI which is content management functionality built to the JSR-170 standard as implemented by BEA’s portal product.

Here what is shown is both the COM and Java APIs into the Services Layer engines. There is also a view into the Image Services Resource Adapter (ISRA) that is a JCA connector that interfaces into Image Services.

Services Layer: The services layer is where the three main engines are shown: Content Engine, Process Engine, and Image Services.

Content Engine is shown here with a few major components or functionality. This is shown by the Rendition Engine that offers up the HTML and PDF publishing service used by the CE. There is also a box indicating the  Web Service Interface as another touch point into the CE besides the COM and Java APIs. There is also a box showing the EAI connector shown as a Business Integration box.

Process Engine is shown here with a few major components. There is also a box indicating the  Web Service Interface as another touch point into the PE besides the COM and Java APIs. There is also boxes indicting the Process Optimization shown as in greater granularity as: Process Analyzer, Process Simulator, and Rules Engine.

Client Applications: There is a box of clients directly connecting into the Services Layer. This is shown here due to the administrative nature of these applications such as the Enterprise Manager that connects into the Content Engine. Keep in mind that this is not a complete logical architecture diagram since it is still high level in its depicting the architecture.

Data Layer: The data layer shows the various repository options for both the CE and IS. It also shows the ability to connect to various existing business/legacy applications. There is also a depiction indicating the connectivity or use of an LDAP server for authentication and authorization since P8 does no identity management.

Magnetic Disk includes both rewritable magnetic disk (NAS, SAN, iSCSI) and WORM magnetic disk (NetApp SnapLock, EMC Centera, etc.) offerings.

---------------------------------------------------------------------------------------------------------------

Content Engine:

The CE is shown here in a low level view. This shows the inner workings of the CE breaking out the main service - Object Store Service – into finer granularity. This takes a view of showing the types of connections between the APIs, clients, databases, etc.

The Event Framework is of note in this diagram. This depicts the Active Content message in that it shows the various means that events can be set and what types of actions they can take based on events to objects such as check-in, promotion, deletion, etc.

The Auto Classification Framework notes the ability to create custom classifiers via the extensibility of it. Out-of-the-box, an XML Classifier is delivered. This is for two purposes. One purpose is to provide an XML classification capability OOTB. The other is to provide an example to start from for building other types of auto-classifiers.

-----------------------------------------------------------------------------------------------------------------------------------------------------

Process Engine:

 

The PE view is to show in greater granularity what is offered in it with the major services. This shows the types of connections to things such as the EAI/Business Integration Services, LDAP, databases, clients, etc.
------------------------------------------------------------------------------------------------------------------------------------------------

Application Engine:

 

This is a low level AE view that is designed to show in greater granularity the various pieces of the AE such as the designers and other user interfaces into the various suites via the AE.

The Web Application Toolkit is what Workplace is built on top of. This is an added level of functionality above what the Java APIs offer a developer for building web based applications.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Image Services

This is a low level IS view.