//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.
--------------------------------------------------------------------------------------------------------------------------------------------------
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.
-------------------------------------------------------------------------------------------------------------------------------------------------
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.
---------------------------------------------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
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.
No comments:
Post a Comment