ECM - FileNet Zone

McLaren Enterprise Engineer Reprographics Server

2012-04-08T09:03:00.000-07:00

McLaren Enterprise Engineer Repographics server polls a job source continually for work items.

It provides following features:

· Watermarking
· Moving files
· Rendering to PDF/HTML/Tiff formats
· Content transfer to the transmittal server
· Properties update
· Title Block Synchronization

Technical details:

· It polls a specific inbox and finds tasks. It processes task based on the configuration information.
· It runs on .Net framework 3.5
· It is used as wither Windows service or a standalone GUI.(Administrator account is needed when installing Reprographics as a Windows service)
· It is built on top of McLaren Work Manager

Hardware/Software detail

· McLaren Work Manager Client (With Office integration and Drawing Manager)
· MS IIS 7.0
· Native apps like CAD, Adobe Acrobat Professional and MS Office (for rendering purpose)
· One repro server needs one reprographics user account.
· Reprographics specific entries are present in the computer registry as following location: HKEY_LOCAL_MACHINE\SOFTWARE\Mclaren\
· Reprographics console is accessed by visiting URL http:///ReproAdmin
· Reprographics server uses log4Net to create and maintain logs and controlled by ReprographicsController.exe.config file available at c:\Program Files\Mclaren\Reprographics\. The log file is located in the user’s profile at c:\Users\\AppData\Roaming\Mclaren\EnterpriseEngineer\logs

Important Configuration Files

JobSources.xml

This configuration file tells the server which inbox to poll for tasks.

TaskPerformers.xml

This configuration file contains settings that guides transformation of native file into various different formats viz. PDF/XML/HTML etc.

Servers.xml

This configuration file tells Repro about the ECM servers [Repository (for Documentum)/ Content Server (for FileNet)] to connect to and provides connection information (configured via Reprographics Connection window).

Preferences

As Webtop in Documentum and Workplace/Workplace XT in FileNet P8 allow users to have set their profile preferences, Reprographics has following types of preferences:

a). General

This type of preferences include polling interval, the default timeout, daily boot time etc.

b). Email Notifications

Sends email notifications to administrator when job fails to complete.

This tab needs SMTP server information to be configured and email account of an administrator who needs to be notified via an email.

How Reprographics Works?

Step1: It finds a Work Task

Step2: Uses configuration information to determine necessary processes (Uses Parameter Gatherers)

Step3: Selects Task Performer* based on Parameter Gatherer information.

* = A component that executes the task usually defined in TaskPerformers.xml

Task Performers render the native files such as CAD into PDF and also performs non-rendering tasks such as change of lifecycle states of documents.

Multiple servers process same queue

Multiple Reprographics servers can poll the same inbox queue. If one server goes down the other will process all tasks. Multiple servers help to handle high volume of tasks. Reprographics server picks the task in FIFO fashion.

Multiple servers process different queues

In multiple Reprographics servers’ scenario (require multiple licenses), each server can poll a different inbox queue as well. JobSources.xml needs to be modified for queue (inbox) information. Specific tasks can be configured for different queues such as change of lifecycle state of documents, PDF publications etc.

There are various benefits of having multiple Reprographics servers:

a). In the event of a server failure, the other available server will continue to process remaining work tasks.

b). Handles high volumes and covers scenarios like large PDF creation

c). Improves processing of package.

Note: Reprographics server can be monitored remotely by visiting a URL such as http:///ReproAdmin/viewQueueContents.aspx

Prioritizing Queues

In case of multiple Reprographics queues, priority can be set on each of them. Repo server process each queue in order of priority. For example, server will finish processing the tasks of highest priority queue first before it starts processing lower priority queue.

By default all queues has priority 1 unless it is set in JobSources.xml.

Following can cause Reprographics server to fail:

a). Corrupt or password protected content

b). Infrastructure and/or configuration issue

e.g: An immutable document cannot be rendered. Network slowness causes timeout for task processing.

Digital Asset Management (DAM)

2011-05-13T21:53:00.000-07:00

Digital Asset Management (DAM)

DAM consists of management tasks related to storage, retrieval and distribution of digital assets. It also refers to the protocol for downloading, renaming, rating, grouping, maintaining and exporting files. The media asset management (MAM) mainly addresses audio, video and animation.

DAM system comprises of computer hardware and software systems that help in the process of digital asset management.

Types of Digital Asset Management Systems

1. Production asset management systems

It focuses on managing assets as they are created for a digital media production viz. animation, 3D movie, video game. They usually include work-flow and project-management features integrated with the storage organization and revision control of changing digital assets.

2. Brand asset management systems

Focus of these systems is on facilitation of content reuse within the organization. The type of content it deals with is sales or marketing related. For example: logos, fonts and product images.

3. Library asset management systems

These systems focus on storage and retrieval of infrequently changing media assets like video or photo archiving.

4. Digital supply chain services push the digital content out to digital retailers (e.g. video, music and game)

DAM Vendors

DAM systems are being offered by various vendors in the market. DAM software may be free open source or proprietary.

Open source software:

Resourcespace: It is a php based solution uses MySql as a backend.

www.resourcespace.org

Proprietary software:

http://digitalmedia.opentext.com/

http://www.widen.com/

http://www-01.ibm.com/software/data/cm/cmgr/mp/edition-enterprise.html

Digital Rights Management (DRM)

2011-05-13T20:11:00.000-07:00

DRM is a method of controlling access to copyrighted material in available digital format. In other words, DRM is a shield around the digital content like videos and music to stop privacy. It is a digital management of rights.

In order to design and implement DRM systems, the following two architectures to be considered:

1). Functional Architecture

This covers the high-level modules of DRM system that together provide an end-to-end management of rights.

The DRM system can be modeled in three areas:

a). Intellectual Property (IP) Asset Creation and Capture This module manage the creation of content so it can be easily traded and includes asserting rights when content is first created.

b). IP Asset Management

To manage and enable the trade of content.

c). IP Asset Usage

To manage the usage of content once it has been traded.

These models needs to be complemented by the functional architecture that provides the framework for the modules to implement DRM functionality.

2). Information Architecture

This covers the modeling of entities within the DRM system as well as their relationships.

DRM Vendors

Below are the some of the DRM vendors

Microsoft

Real Network

Macrovision

IBM

Seclore

Seclore - Information Rights Management
Seclore FileSecure’s IRM connector for IBM FileNet® empower enterprises with the ability to robustly secure and monitor access to content and information within and outside of IBM FileNet® without any compromise to collaboration and way people work.

http://www.seclore.com/ibm_filenet.html

DRM from IBM

IBM has developed two solutions to enforce DRM at low level:

a). DRM-JVM

In this solution digital rights management has been enforced at Java virtual machine(JVM) level. DRM-JVM does not affect the non DRM solutions.

b). WebGuard

This solution enforces copyrights at the browser level.

What is Web 2.0?

2011-04-06T19:16:00.001-07:00

Web 2.0

The term Web 2.0 is generally used for those web applications (sites) that facilitate collaboration, information sharing on the World Wide Web (WWW). Examples of Web 2.0 are wikis, blogs, video sharing sites, social networking etc.

The difference between normal web site and Web 2.0 site lies in the way users interact with Web. A Web 2.0 site allows users to interact and collaborate with each other in a virtual community while users of websites are limited to the passive viewing of the content available on them.

Although the term Web 2.0 suggests a new version of World Wide Web, it does not refer to an update to any technical specification, but rather to changes in the way software development and user community use the Web.

For more information visit http://en.wikipedia.org/wiki/Web_2.0

Microsoft Sharepoint 2010

2011-04-01T01:53:00.000-07:00

Below are some new features/improvements available in MSP 2010

· Improved Records Management and Digital Asset Management.

· Advanced Routing – SP System determines which library/folder the new submitted document should be saved based on the associated meta-data.

· Document Set – Allows grouping of multiple items in order to consolidate them. For example: documents related to one project can be grouped.

· Search function has been improved with the features like ‘relevance improvement’, people search and FAST search.

· Business processes improved

· Chart Web part have been introduced as an aid to the data visualization.

· Workflow designer has been improved.

· Moving of the Workflow from test to production environment has been easy in 2010 which was not in 2007.

· Export/Import from Visio 2010 is available. [Note: SP stores most of the contents in SQL DB instead of the file system]

· Sharepoint 2010 is 64 bit means it requires 64-bit Windows Server 2008 and 64-bit SQL Server 2005/2008.

· Service applications have taken place of Shared Service provider (SSP).

· Sharepoint 2010 Support Major Browsers.

· New Content related feature like Rich Media Management, Flexible Records Management and Content organizer

· Tags, Tag Clouds, Tag Profile, Note board, recent activities, enterprise Wikis, ratings and Keyword suggestion are new community features.

· Business connectivity services (BCS), Visio services and Access services are introduced as composite(mash-up) features. These services help in pulling data from different sources and combining it in a single place.

Single-Threaded Apartment (STA)

2011-03-13T19:20:00.001-07:00

Single-Threaded Apartment (STA)

In .Net, the main method used to be preceded by the following attribute declarations:

[STAThread]

static void Main() {

What is its significance?

After going through multiple blogs and sites I have concluded that if you are not using COM and none of the APIs you are going to use in your application makes use of COM in any way then don’t pay any attention to the concept of APARTMENT.

A thread must use the STA model if it intends to display any GUI. This is the reason why main method has [STAThread] attribute before it.

What is an Apartment?

A process is a collection of virtual memory space, code, data, and system resources.

A thread is code that is to be serially executed within a process. [A processor executes threads, not processes, so each application has at least one process, and a process always has at least one thread of execution, known as the primary thread. A process can have multiple threads in addition to the primary thread]

In general, the simplest way to view the COM threading architecture is to think of all the COM objects in the process as divided into groups called apartments. A COM object lives in exactly one apartment, in the sense that its methods can legally be directly called only by a thread that belongs to that apartment. Any other thread that wants to call the object must go through a proxy.

What is Single and Multi Thread Apartment?

Single-threaded apartments consist of exactly one thread, so all COM objects that live in a single-threaded apartment can receive method calls only from the one thread that belongs to that apartment. All method calls to a COM object in a single-threaded apartment are synchronized with the windows message queue for the single-threaded apartment's thread. A process with a single thread of execution is simply a special case of this model.

Multithreaded apartments consist of one or more threads, so all COM objects that live in an multithreaded apartment can receive method calls directly from any of the threads that belong to the multithreaded apartment. Threads in a multithreaded apartment use a model called free-threading. Calls to COM objects in a multithreaded apartment are synchronized by the objects themselves.

SHFUSION.DLL - Assembly Cache Viewer

2011-03-10T20:11:00.000-08:00

SHFUSION.DLL - Assembly Cache Viewer

Shfusion.dll
This file generally lies in the c:\windows\microsoft.net\framework\ folder. This file is responsible for showing the c:\windows\assembly (.NET GAC folders) as a special folder which does not allow any I/O operations like copy/delete etc.

In order to see the c:\windows\assembly folder as a normal folder just unregister the shfusion.dll. You need to be an administartor on the machine for running regsvr32 command to unregister this dll.

In order to switch back assembly folder to the original (special) view just register the shfusion.dll using regsvr32 command. Visit http://msdn.microsoft.com/en-us/library/34149zk3(v=vs.71).aspx for more information.

Applies to the .Net Framework up to 3

Access List and Default Item Access List(DIAL) - FileNet CS

2011-02-21T21:51:00.000-08:00

Access List [This is the list which governs the access of a user to specific objects]An access list can control access on a user-by-user basis, the lists would become long and difficult to maintain if they listed all possible users by name.For ease of implementation of t he access control, the library system allows assigning access rights to groups, because groups contain sets of users who have common access requirements.

Because a user may belong to more than one group in a library system, access control is determined by a user's active group, that is, the group in which a user is currently working. Thus, when users change their active group, their access rights to objects also change accordingly. Using groups to control access greatly simplifies security. Suppose, for example, that there are seventy users in a library system, but these users all fall into three work groups: employees, supervisors, and a personnel department. Since there are also three groups with those same names, the access list for a document that corresponds to an employee's personnel record would need only three entries (one for each group), rather than seventy (one for each
individual user). If groups are created to match the way people work in an organization, their use in controlling access can ensure people will read and modify only the appropriate information.

An access list contains information about the users and groups who have been assigned specific access rights to a particular object. In CS Explorer, this information is displayed as Access Control object properties. Each Access Control object contains three pieces of information:
• The name of a user or a group
• The type of name
• The access rights granted

By default, a library system uses the following search pattern when determining a user’s access rights to a particular object and assigns the first access rights that apply:

1. Checks to see if the user is a member of the Administrators group.
2. Checks in the object's access list for an entry under the user name.
3. Checks in the object's access list for an entry under the user's active group.
4. Checks the access rights assigned to the General Users group, if included in the access list.
5. Assigns the user access rights of None.
Notice that this search pattern ensures that active members of the Administrators group always receive Admin access; thereafter, access rights specifically granted to a user take precedence over those granted to a group.

Default Item Access List [This list get sused when the user adds document into CS]Another way a library system can help users control access to their files is by inserting default entries in document access lists so that the user does not have to provide the same set of entries each time he or she adds a document.

You can specify a set of default item access list entries for each user in his or her User object. Then, each time that user adds a document to the library system from any user interface, the access list of the Item object is filled in with those specified defaults. Of course, to cover special cases, users can always change the access list of any documents they add, but they do not have to start from scratch with each document.
In the same way that you add entries to the default item access list in the User object, you can also specify them in Group objects and the System object.

Thus, the access lists of documents do not necessarily have a standard set of default entries. The library system does add default entries to the document's access list as the document is added, but to determine these defaults, the library system will check for entries in the Default Item Access List properties in the following objects and use the first such list with any entries:

1. The User object
2. The Group object for the user's active group
3. The System object

Version Numbering in FileNet P8 CE

2011-02-09T22:34:00.000-08:00

Each document version is assigned a number that reflects whether the document is a major or minor version. This number is automatically assigned and changed by the Content Engine whenever a versioning action, such as a checkout, takes place that changes the version status of the document.
The version number is unique in the document version series and is actually comprised of two properties—the major version number and the minor version number. These properties are described in Versioning properties.
The numbering rules are fairly simple:

A minor version always has some number other than zero as its minor number. Both 0.1 and 4.32 are examples of a minor version. Reservation versions are always assigned a minor number.
A major version always has an integer other than zero as its major number, and always has a minor number equal to zero; for example, 5.0.

As you can see, these two numbers can be joined into what looks like a single number. Enterprise Manager and application such as Workplace sometimes display these numbers joined together with a decimal divider, with the major number coming before the decimal and the minor number after. In other places like the list of properties in the object property grid, the two properties are listed separately.
If a new document is first checked in as a minor version, its version number becomes 0.1. The next version in this series would be 0.2 if a minor, and would be 1.0 if it is checked in as a major version.
If a new document is first checked in as a major version, its number would be 1.0. The second version in this series would be 2.0 if a major version, and would be 1.1 if it is checked in as a minor version.
A document in the reservation state is always a minor document and has a minor document number. For example, if you check out a document numbered 2.0, the resulting reservation version is numbered 2.1. If you check out a document numbered 2.1, the resulting reservation version is numbered 2.2 (because a reservation is always a minor version).
It is on checkin that users can decide whether to check in the Document as a minor or as major version. A reservation number therefore stays the same if it is checked in as a minor version, and changes if it is checked in as a major version. For example, a reservation numbered 2.1 is still numbered 2.1 if it is checked in as a minor version. If the same reservation numbered 2.1 is checked in as a major version, its number changes to 3.0

Versioning properties

Several document class properties are important to document versioning. Each document version is either a major version or a minor version and is automatically assigned a major number and a minor number. See Version numbering for more about how the major and minor numbers make up a document version number. See What appears in folders? for details about which version of a document shows up by default in Enterprise Manager and applications such as Workplace XT. See Versioning actions to understand how actions like checking out or promoting a document determine the properties described in this topic.
Content Engine maintains the following read-only properties related to versioning:

Major version number

A major version is one that

has been approved as released, or
was released in the past but has now been superseded by a more recently released version.

Released major versions are typically designed to be available to a wide range of users. Access to superseded major versions is typically more restricted, such as to a select group of authors and reviewers.
Major versions always have a minor number equal to zero. For example, a document with a major version number of 2 and a minor version number of 0, sometimes displayed together with the major number first, as in 2.0, is a major version.
If two-level versioning is used, the major number holds the current major version level of this document version series.
If single level versioning is used, all versions of the version series are major versions. The only exception is that reservations are always given a minor number, which in single-level versioning is therefore always 1. As soon as the reservation is checked in, the minor number goes back to 0 while the major number is incremented by 1.

Minor version number

A minor version is one that has not been approved and released as a major version. The most recently checked in minor version is marked in process. There can be only one in process version in a version series. Older minor versions are marked superseded, and there can be many superseded versions. Access to minor versions is typically restricted to a select group of authors and reviewers. A reservation document (the editable document version created by a checkout) is always a minor document.
A document is a minor version if its minor number is 1 or more (that is, not equal to zero). For example, a document numbered 2.1 has a major version number of 2 and a minor version number of 1 and is therefore a minor version.
If two-level versioning is used, the minor number holds the current minor version level of this document version series. Versions that are major versions (superseded or otherwise) have a minor number of zero. Versions that are minor have some number other than zero for the minor number.
If single-level versioning is used, the minor number is always equal to zero, with the one exception of the reservation as previously described.

Version status

Content Engine provides four versioning states that are automatically applied as a document version series goes through various defined stages. These states are released, in process, reservation, and superseded. Each of these states can be associated with a security template, providing easy control over the permissions granted on the document as it passes into a particular versioning state.

Released: A major version that is generally made available to all users. Only one version of a document in a given version series can be in the released state at a time.
In process: A checked in minor version, which is typically made available to a restricted set of authors and reviewers. Sometimes referred to as a draft. Only one document in a version series can be in process at a time. When a reservation document gets checked in and becomes the new in process document, the previous in process document becomes superseded.
Reservation: A document whose content is currently being edited. A reservation is a full-fledged version and can be saved in the object store indefinitely. Even though you can edit both the properties and content of a reservation, there is nothing unstable about it; it does not act like an unsaved word processing document that is in danger of being lost if it is closed without being explicitly saved to disk. The term reservation is meant to convey that the author who is editing the document has reserved it for his or her own use. There can never be more than one reservation in a version series, because only the current version can be checked out. Reservations are always minor versions. Users can save the content of the reservation document one or more times before checking it in. Do not confuse reservation with Reserved.
Superseded: A major or minor version that is no longer the most recent version. A major released version becomes superseded when there is a more recent major released version. A minor becomes superseded when there is a more recent minor in process version. There can be many superseded major and minor versions in a version series.

These version states are actually stored as integers and are sometimes displayed as integers by Enterprise Manager and applications such as Workplace:

Released = 1
In Process = 2
Reservation = 3
Superseded = 4

The text values ("Released" and so on) are associated with the integers by the Version Status Lookup Custom Object. You can edit this custom object to change the strings to some other value. You can, for example, change "Released" to "Public version" or "In Process" to "In Progress".
For information about how security policies can be designed to automatically apply these changes of permissions to versions as they change from state to state, see Security policies.

Current version

Current Version is a property that defines which version in a version series is the most recent version, other than the reservation. (The reservation cannot be the current version.) The value of this property is used by events, folder references, and other server or client-based processes that act on the latest version.

Reserved

Reserved is a property that is set on the current version when it is checked out. The term "Reserved" is meant to convey that the current version is no longer available to be checked out. Do not confuse with reservation. When the Reserved property of the current version is set to True, there must also be another version that is the reservation.

FileNet Content Services Concepts - Part 6

2011-02-06T22:38:00.000-08:00

Property Manager The components in the library system that store and maintain in a database a library system's objects and properties. These objects and properties identify and describe stored documents and unstored items. They also describe users, groups, searches, and system components. Each library system has its own Property Manager. The Property Manager is roughly equivalent to the database engine, but has a slightly larger conceptual purpose. For example, each of the library systems that happens to share a database engine is said to have its own unique Property Manager.

Property repository A Microsoft SQL Server database or Oracle tablespace that contains the objects and properties for a single library system. The objects and properties identify and describe stored documents and unstored items. They also describe users, groups, searches, and system components.

The documentation generally refers to a SQL Server database or Oracle tablespace as a property repository only after you have installed the associated library system and applied its initial changes to the database or tablespace. Prior to library system installation, the documentation uses database or tablespace rather than property repository (for example, “To create an Oracle tablespace:").

Property server The server where the library system database engine is installed. Typically, this server is also the initial storage server, but under certain configurations, may be a standalone database server instead.

Storage Manager The library system service that processes operational requests (for example, to check in or check out) and stores version files controlled by the library system.

Storage category To a user, such a category typically describes a type of file (for example, Word Docs, Payroll Records, Memos). To an administrator, storage categories provide a way of controlling load balancing in the various storage repositories. Storage category names are determined by an administrator to reflect the working environment at a particular site. One or more storage categories may be assigned to a storage repository and administrators can change these assignments as load requirements change.[Can be visualize as document class]

Storage repository A storage area (that is, a directory) for specific version files controlled by the library system. Each file is stored according to a storage category, which is assigned when the file is added to the library system as a protected item. A storage repository may be assigned numerous storage categories for a particular installation of a library system.

Storage server Any server where initial or additional services for a library system are installed.

Verity K2 Master Admin The Verity component that governs all Content Search Managers for a library system.

Verity K2 Master Admin Server The server where the CS installer places the Verity K2 Master Admin that governs the Content Search Managers for a given library system.

Archive category Describes a way of handling version files that are moved offline during automatic or manual archiving. Each protected item is given an archive category (for example, Archive To Tape) when it is added to the system. Each archive category is assigned to a specific storage directory called an archive repository.

Archive repository A storage area (that is, a directory) for specific system-controlled version files that are moved offline. The archive repository is where the files are held while awaiting archive storage or destruction outside of the library system. Archive repositories can be described as reclaimable or no reclaimable. Typically, files that are moved offline through a reclaimable archive repository are more easily reclaimed for use at a later time. Each archive repository may be assigned numerous archive categories.

Content Search Manager A software service that contains the program files required to make content searching for version files available with the library system.

Content search repository A named collection of files identifying versions that have been indexed so that users can find those versions based on the actual contents of the version files. You must add at least one of these content search repositories for each Content Search Manager.

FileNet Content Services Concepts - Part 5

2011-02-06T22:36:00.000-08:00

Replication Services Overview

Replication Services gives your documents greater availability across your enterprise, automatically and without compromising document integrity. Instead of manually creating and maintaining the necessary user accounts and documents on separate libraries, replication automatically copies the documents and related security to another library system.

Replication Services provides a way to make documents and items in one library system available to other library systems. Replication Services automatically copies documents, items, and their security to additional specified library systems. As documents are checked out, updated, and checked in again, the changes are synchronized across the other libraries.

When a document is replicated, both the file content and the property values for standard properties and existing custom properties of the document are copied into the library systems participating in Replication Services. Users can quickly locate and access a replicated document anywhere in any replicated library. All instances of replicated documents or folders in any library system are periodically synchronized with any alterations to the original document or folder.

However, the synchronization is not immediate. That is, Replication is an asynchronous store-and-forward system. Changes are logged into a queue for processing, and then propagated to the replica libraries. The processing may take place almost immediately, or it may take place only during certain hours of the day, depending on your configuration parameters, the number and type of changes requested, the network load, and the availability of the replica libraries. For example, if a replica library is offline for maintenance (or a power failure), the update cannot be completed until the library is available again.

A replicated document's current status is reflected on all the participating library systems: if checked out, a document will be marked as checked out on all of these library systems. When a new version is checked in, that new version is replicated to all the participating library systems. Replication Services runs independently of the other library system services. Thus, Replication Services can continue running while other library system services are stopped and restarted and can automatically resynchronize with these library system services when they restart. Using Replication Services can have a profound impact on your library system configurations and the hardware and software resources required. Take time to carefully plan your system before you implement replication in your network.

Additional point: You must copy Document Classes and Controlled Vocabulary Lists (CVLs) from one library to another using the import and export tools available in CS Explorer.

FileNet Content Services Concepts - Part 4

2011-02-06T22:34:00.002-08:00

Deleting Sessions

In a library system, an active session is the open session that a user is currently working in. There are actually two sessions involved when a user is logged in to a library system via a Content Services client application, such as IDM Desktop or CS Web Admin environment. One is the database connection session, and the second is the Content Services library session.

When a CS client application exits or is killed, the corresponding database connection session is deleted from the database. You can also delete all the database connections at once by stopping and restarting the database. If a database connection session is deleted, then any corresponding active CS library session is said to be an orphan session.

CS library system sessions are tracked by CS Explorer but cannot be removed by it. Neither stopping and restarting the database or CS services will delete an orphan session. Nor will rebooting a workstation where a CS client application is running. To remove these orphan CS library sessions, you can invoke DSSTOP on the server where the library system is resident. Alternatively, you can simply allow the daemon running on the database custodial server to periodically check for suspended sessions. The daemon will remove any orphaned sessions that are more than two days old. To find out what sessions are open in a particular library system and to see whether these sessions are active or suspended, you can check the status of the Sessions object using CS Explorer.

Resetting the Session ID

The library system maintains a unique session ID for each library system session. The session ID is incremented each time a user opens a new session. Over time, it is possible to exceed the limit of approximately 2 billion (231) session IDs.

To avoid an overflow condition, we recommend that you periodically check the value of the Session Number property in a Session object (the value of this property is the session ID). When the value of the Session Number property approaches 2 billion, you should reset the session ID to 0.

To reset the session ID:

1. Stop the library system and database services.

2. Restart the database services.

3. Using your SQL query tool (SQL Server Query Analyzer for SQL Server or sqlplus for Oracle), reset the session ID to 0.

• For SQL Server enter:

use system_name

delete from session

update numid set se_id_num=0

• For Oracle enter:

delete from system_name.session;

update system_name.numid set se_id_num=0

4. Restart the library system services

FileNet Content Services Concepts - Part 3

2011-02-06T22:34:00.000-08:00

Secure Document Delete

With the Secure Document Delete feature you can scrub your sensitive document files to prevent any possibility of recovery via disk recovery tools. Scrubbing means to overwrite its contents with a byte pattern before actually deleting the file.

Scrubbing means that the file's entire content is overwritten by a byte pattern before the file is actually deleted. Secure Document Delete does not delete files from client machines. To ensure secure delete functionality on servers containing library system components, do not install client interfaces (such as IDM Desktop) on those servers.

Neither Replication Services nor Web Services scrub files during add, checkin, and checkout operations. For simple delete operations as may be desired during a “purge” process however, Secure Document Delete is applied on all servers that have this feature turned on.

You can configure the Secure Document Delete feature for each Storage Manager by selecting one of the options described below.

Level	Description
No Secure Deletes	Ordinary delete. Files are not overwritten before being deleted.
One Scrub	Files are overwritten with zeroes once before being deleted. This level corresponds to the Clear definition of the DOD 5220.22-M specification.
Three Scrubs	Files are overwritten once with an arbitrary character, again by the character's complement, and finally by a random character before being deleted. This level corresponds to the Purge or Sanitize definition of the DOD 5220.22-M specification.

The initial and additional (remote) Storage Managers of a library system are each separately configurable with respect to secure deletes. Whether an item (document) is securely deleted depends on the secure-delete setting of all the Storage Managers that govern the storage repositories where the versions of the item are stored.

When an item is added to a library, it is given a Storage Category, which is associated with the storage repository where the versions of the item will be stored. As one storage repository fills up, the system administrator will assign the Storage Category to another storage repository. Thus, over time, different versions of the same item may end up in different storage repositories.

To ensure that an item is securely deleted, make sure it is given a Storage Category all of whose associated storage repositories will only be on servers where the Storage Manager is configured for secure deletes. Beware that if even one of the storage repositories associated with the Storage Category is on a server whose Storage Manager is not configured for secure deletes, then any versions of the item that are stored on that server will not be securely deleted.

Secure Document Delete Limitations

On UNIX platforms, files larger than 2 Gbytes will not be overwritten and must be scrubbed using special tools. On Windows platforms, files will be scrubbed securely up to the full Windows 64-bit limit.

Secure Document Delete does not scrub property data in the database; this remains the job of the database administrator and the database itself. Microsoft SQL Server and Oracle do not scrub database data during row or table deletion.

You cannot obtain Secure Document Delete functionality on compressed disks or files. Do not use defragmentation tools on the disk containing the stored document files. Such tools move the files on the disk without pre-scrubbing them, making secure deletes unsupportable.

Some database metadata (such as file names, Item IDs, Version IDs) are not scrubbed in subtle places. For example, when a search query is performed, even on the server, a temp file is used to store the results. When the query ends, the temp file is deleted (but not securely). Database metadata is generally insecure; even Microsoft SQL Server and Oracle databases cannot do secure metadata deletes.

The Windows pagefile and UNIX swap files may include memory images that need to be paged to disk, and the memory image may include the files you are copying or writing. The Secure Document Delete functionality cannot scrub these files.

Reformatting a hard disk may not overwrite data on the disk. If you reformat a disk containing storage repositories, you should use other tools to scrub the disk clean of file data.

The uninstall command (dsuninst.exe) does not scrub storage or index repository files. Activities such as the actions of the executable files that perform during installs and upgrades, the use of tools, and utilizing configuration code, do not carry out secure deletes. For example when DLLs are copied to a temp directory, they are not scrubbed when they are removed. Secure Document Delete does not work on Hierarchical Storage Manager extended drives. HSM controls access to files on media and cannot guarantee scrubbing in the process of a move or purge

FileNet Content Services Concepts - Part 2

2011-02-06T22:32:00.002-08:00

Library System Security

One of the powerful feature of the library system is the security it provides for your important information. Each time you or any other user adds a document to the library system, you determine the document's descriptive properties and its associated version files and properties that users and groups will be able to access. You provide this information using the document's Access List property. For further security, there is also an Access List property for all users and groups. Three objects commonly referenced by users and administrators contain an access list: the User object, the Group object, and the Item object. However, access rights to entities without access lists (such as versions) are passed down through “parent” objects (such as the Item object). So, the library system provides a simple way to set up and maintain access control, yet allows this security to be as controlled or permissive as necessary. There are five levels of access rights in a library system:

Access Right	Privileges granted
None	No access. If no other access level is stated in the access list, access rights of None are assumed. An access level of None can also be explicitly stated in an access list.
Viewer	Generally, the ability to view the object properties or to make copies of the associated versions.
Author	(Applies to documents and versions only) Viewer access rights plus the ability to checkout ,check in and copy associated versions and modify property values for the version. In addition, you may be allowed to modify designated custom property values for the document.
Owner	Author access rights plus the ability to delete documents, modify security and modify most properties.
Admin	Owner access rights plus the ability to modify all property values. Active members of the Administrators group are automatically assigned Admin access rights to all properties, even though their names do not appear in any access lists. Users who are not members of the Administrators group can be explicitly assigned an Admin access level to the properties associated with particular objects.

DIAL – Default item access list

Access List Defaults

To ensure that each access list contains initial entries, a library system provides some defaults in the User, Group and Item object. In User and Group object access lists, these defaults are standard entries that are always added, as shown in the following:

Name Type Access Level

(Added By User) User Admin

(User's Name) User Owner

General Users Group Viewer

The Added By User value is the user who added the object to the library system. This user and any user with Owner or Admin access rights can modify the values after the User or Group object has been created. The Administrators group always has Admin access rights, even though these rights are not displayed in the access list.

Default Item Access Lists

Another way a library system can help users control access to their files is by inserting default entries in document access lists so that the user does not have to provide the same set of entries each time he or she adds a document. You can specify a set of default item access list entries for each user in his or her User object. Then, each time that user adds a document to the library system from any user interface, the access list of the Item object is filled in with those specified defaults. Of course, to cover special cases, users can always change the access list of any documents they add, but they do not have to start from scratch with each document. In the same way that you add entries to the default item access list in the User object, you can also specify them in Group objects and the System object.

1. The User object

2. The Group object for the user's active group

3. The System object

To understand how default item access lists work, consider the following example. At the law firm of Hunter and Bowers, senior lawyer Sarah Black is using IDM Desktop to add an item to a library system. She knows that her system administrator has given her active group (Attorneys) the default item access list (shown below), which will be applied to all documents added by the group's members.

Name Type Access Level

Attorneys Group Author

Managers Group Author

Paralegals Group Viewer

The system administrator has left the Default Item Access List property blank in Sarah's User object because Sarah always wants the default access list for her active group to be applied. (Likewise, whenever Sarah changes her active group, the library system will apply the default item access list of her new active group.) She also realizes that since the default access list at her active group level does not mention her name specifically, she will receive the program default access rights for any user who adds a document and Owner access rights to the document that she is adding to the library system. And with Owner access rights to the new document, she can modify the entries in the document's access list at a later time if necessary.

FileNet Content Services Concepts - Part 1

2011-02-06T22:32:00.000-08:00

The Library System

Content Services (also called the library system) provides server-based enterprise content management (ECM) that can be accessed via a client interface using applications such as FileNet IDM Desktop or FileNet Web Services. An enterprise, especially if it's spread across various sites, may have multiple library systems, depending upon sizing and load balancing considerations.

A typical Content Services installation comprises the following components:

• One or more library systems.

• One or more administrative clients.

• One or more ECM clients (such as IDM Desktop).

• One or more application solutions (such as FileNet Web Services for intranet/internet access).

As you can see in the following illustration, each library system has a set of sub-components that you install and configure to provide the services for your various client-based users.

Each library system acts as an information storehouse.

· The Property Manager stores and manages object properties (users, groups, system, and custom properties) and metadata describing your catalogued documents.

· The Storage Manager stores the actual documents and process requests.

· The Content Search Manager provides document content-based indexing and searching capabilities.

· CS Replication Services, which allows you to replicate documents across multiple library systems.

You have the option to locate your database on a standalone property server. In this configuration, the initial Storage Manager, Content Search Manager, and Replication Services would be located not on the property server, but on the initial storage server.

Protected Items

When you add a document to a library system, you usually add it as a protected item. It is called “protected” because the library system physically stores the document, thereby protecting it from unauthorized access, inadvertent removal, and more. Protected items can be documents that were created by any application (for example, word-processing documents, financial spreadsheets, images, audio, tables, and so on).

Unprotected Items

A library system also lets you control and manage unprotected items (external documents), which are items that are not physically stored in the library system but are tracked for easy management. This capability is especially useful for items that are stored in special locations, yet still require version tracking or controlled access. Some examples are: magnetic tapes, printed technical manuals, printed engineering drawings, and software source code listings. Although the unprotected items added at most sites represent these kinds of physical objects, unprotected items can also be electronic files that you do not want to store in the library system.

FileNet Content Services Features

2011-02-06T22:29:00.000-08:00

Network-wide Search and Retrieval

FileNet Content Services (CS) systems allow documents to be identified using plain language titles and property names, not cumbersome file names. End users can search for documents based on their properties and/or their content. Regardless of the user's location or the file's location, complex path commands with coded document names are never required. Documents are checked out of and checked in to the FileNet CS system for updates and revisions. One simple end user command transparently saves, tracks, and archives any document.

Logical, Not Physical, Storage Pointers

Unlike conventional document management packages that rely on physical file locations, a FileNet CS system does not require users to have any knowledge of where documents are actually stored. In fact, users are shielded from that knowledge, providing an added layer of security for the documents and the network. Document management systems that use physical pointers require constant supervision and cumbersome revision as networks grow and change.Moving files, adding users adding or changing directories means updating every single workstation individually. With a FileNet CS system, such system changes can be handled centrally by the network administrator.

Object-Oriented Approach

A FileNet CS system encapsulates all types of files and objects. Each object is described by properties such as description, security, and administration. Actions are performed against objects using these properties as variables. In this way, an ordinary file becomes an “intelligent” document because, regardless of how or where it is used, the document retains its properties and always knows who is authorized to view it or make edits, where it is to be stored on the network, and how it is to be administered and archived.

Version Control

When a user opens a document for editing, it is designated as checked out. The user is always provided a copy of the particular version of the document, and the original copy of that version remains protected. Other users who try to access a document version that is checked out are notified that it is checked out and by whom. While the document is checked out and being modified, users can view the latest checked-in version of the document. When the user is finished working with a checked out version, he or she can check it in. The FileNet CS system retains the old version and automatically saves the checked in document as a new version. Once checked in, the old and new versions of the document become available for check out to other users. When users access the document, they are free to check out the most current version or go back to older versions as needed.

Multilevel Security

An access control list is created for each document added to a FileNet CS system. This access control is part of the document's properties and is independent of the document's location on the network. In this way, authorized users have access to the information they need, no matter where they or the documents are physically located. Yet all stored documents are well protected, because only the documents that each user is authorized to see will be displayed as the result of a search.

A FileNet CS system controls who can create new versions of any given document, regardless of data type, application used, or storage location. Security levels determine access rights such as Owner, Author, Viewer, or None. The only access to documents is through the FileNet CS system. File names are encrypted and users are prevented from bypassing the FileNet CS system to access files via the network operating system. CS administrators should not share the directories where FileNet file are located.

ECM Administration Tools

FileNet CS systems include a Windows® based administrative tool. ECM administration tasks such as adding new servers, designating new storage locations, or adding new users and groups can be performed at any time, no matter how many users are online. In addition, a web browser-based version of the administrative tool that includes a subset of the windows-based administration tool is available for administrators who want mobile access to library system properties and the ability to start/stop CS servers remotely.

Flexible Open Technology

CS is designed to work with virtually every combination of user interface, application, and hardware/software. Creation and maintenance of general office documents (including enterprise, departmental, workgroup, and personal documents), legal document management, email, as well as document imaging may all be handled through a common repository. This means that no matter how many platforms or environments are used across the network, all enterprise applications are interoperable. Additionally, any enterprise can take advantage of FileNet IDM Desktop (and, if necessary, CS API programming functions) to build custom enterprise applications as future needs emerge.

Load Balancing and Scalability of Distributed Services

No matter how an organization's workload grows and changes across departments or divisions, the FileNet CS system's queue management and load balancing features ensure a consistent working environment for end users.

Documentum Foundation Classes 6

2011-01-12T22:55:00.001-08:00

DFC (Documentum Foundation Classes 6.0)

DFC is a key part of the Documentum software platform. While the main user of DFC is other Documentum software, you can use DFC in any of the following ways:

• Access Documentum functionality from within one of your company’s enterprise applications.

For example, your corporate purchasing application can retrieve a contract from your Documentum system.

• Customize or extend products such as Webtop.

For example, you can modify Webtop functionality to implement one of your company’s business rules.

• Write a method or procedure for Content Server to execute as part of a workflow or document

lifecycle.

For example, the procedure that runs when you promote an XML document might apply a transformation to it and start a workflow to subject the transformed document to a predefined business process.

You can view Documentum functionality as having the following elements:

Repositories One or more places where you keep the content and associated metadata of your organization’s information. The metadata resides in a relational database, and the content resides in various storage elements.

Content Server

Software that manages, protects, and imposes an object oriented structure on the information in repositories. It provides tools for managing the lifecycles of that information and automating processes for manipulating it.

Client programs

Software that provides interfaces between Content Server and end users. The most common clients run on application servers (for example, Webtop).

End Users People who control, contribute, or use your organization’s information. They use a browser to access client programs running on application servers.

Documentum Foundation Classes (DFC) lies between Content Server and clients. Documentum Foundation Services are the primary client interface to the Documentum platform. Documentum Foundation Classes are used for server‑side business logic and customization.

DFC is Java based. As a result, client programs that are Java based can interface directly with DFC.When application developers use DFC, it is usually within the customization model of a Documentum client, though you can also use DFC to develop the methods associated with Content Server functionality, such as document lifecycles.

In the Java application server environment, Documentum client software rests on the foundation provided by the Web Development Kit (WDK). This client has a customization model that allows you to modify the user interface and also implement some business logic. However, the principal tool for

adding custom business logic to a Documentum system is to use the Business Object Framework (BOF).

BOF enables you to implement business rules and patterns as reusable elements, called modules. The most important modules for application developers are type based objects (TBOs), service based

objects (SBOs), and Aspects. Aspect modules are similar to TBOs, but enable you to attach properties and behaviour on an instance‑by‑instance basis, independent of the target object’s type.

BOF makes it possible to extend some of DFC’s implementation classes. As a result, you can introduce new functionality in such a way that existing programs begin immediately to reflect changes you make to the underlying business logic.

The Documentum Content Server Fundamentals manual provides a conceptual explanation of the capabilities of Content Server. DFC provides a framework for accessing those capabilities. Using DFC and BOF makes your code much more likely to survive future architectural changes to theDocumentum system.

Where Is DFC?

DFC runs on a Java virtual machine (JVM), which can be on:

• The machine that runs Content Server.

For example, to be called from a method as part of a workflow or document lifecycle.

• A middle‑tier system.

For example, on an application server to support WDK or to execute server methods.

For client machines, Documentum 6 now provides Documentum Foundation Services (DFS) as the primary support for applications communicating with the Documentum platform.

Acronyms

DFC Documentum Foundation Classes

TBO Type based object

SBO Service based object

WDK Web development toolkit

BOF Business object framework

Microsoft Dynamic Langugage Runtime (DLR)

2010-12-19T16:38:00.000-08:00

The Dynamic Language Runtime (DLR) is a set of libraries built on the CLR to support dynamic language implementations on .NET. A key value proposition of the .NET CLR is supporting multiple languages and allowing them to inter operate with each other. Dynamic languages have become very popular in the last several years. Customers want to use their favorite dynamic language and have great .NET interoperability for building applications and providing scripting for applications. The DLR makes it very easy to develop dynamic languages on .NET.
The DLR provides three key components:

language implementation services with language interoperability model
dynamic language runtime services with fast dynamic dispatch and library support
common hosting APIs across languages

The key goals of the DLR are making it easy to

port dynamic languages to .NET
add dynamic features to your existing language
author libraries whose objects support dynamic operations
employ dynamic languages in your applications and frameworks.

DLR hosting APIs
The DLR Hosting API is a programming interface that allows one language’s code to execute in another
language. It helps in using a Dynamic Language’s Code in a Static Language.

Dynamic Languages - Outside .net family of languages. For example: Ruby or Python
Static Languages - .NET languages like VB.net, C#.net etc.
For more information please visit http://dlr.codeplex.com/

K2 BlackPoint

2010-11-08T20:56:00.000-08:00

K2 BlackPoint is used to create new workflow using Microsoft Sharepoint and Microsoft Infopath.

It has two designers a). K2 Studio and b). K2 Web Designer

Benefits:
a). Visual tools to create worflow.
b). No coding required.
c). Tools that can be used by non developer.

For more information visit http://www.k2.com/en/blackpoint.aspx

Generate barcodes using barcode4j

2010-10-13T21:30:00.000-07:00

Barcode4J is a barcodes generator written in Java. It's free, available under the Apache License, version 2.0.It supports generating 1D and 2D barcodes of various types.

a) Implementations

* 1D barcode implementations
          o Interleaved 2 of 5
          o Code 39
          o Code 128
          o Codabar
          o POSTNET & more
* 2D barcode implementations :
          o PDF 417 (ISO/IEC 15438:2001(E))
          o DataMatrix (ISO/IEC 16022:2000(E))

b) Support for multiple formats:

It supports various file formats viz. SVG, EPS (Encapsulated PostScript), Bitmap images (such as PNG or JPEG), Java2D (AWT), Text (for testing and debugging only).
http://barcode4j.sourceforge.net/2.0/output-formats.html

c)Barcode Servlet with support for SVG, EPS and bitmap output

d) Command-line interface
barcode4j has command line support so you can generate barcode by executing a command on command line.

e) Plug-ins/extensions for third-party products:
          o Apache Xalan: SVG-generating XSLT extension
          o SAXON XSLT Processor : SVG-generating XSLT extension
          o Apache FOP: support as fo:instream-foreign-object

For more information go to http://barcode4j.sourceforge.net/

IBM Classification Module and Content Extractor

2010-10-06T20:47:00.000-07:00

IBM® Classification Module

IBM® Classification Module helps organize unstructured content by analyzing the full text of documents and e-mails and applying rules that automate classification decisions.

IBM Classification Module reduces the burden of manual decision making that is done by employees by accurately and automatically organizing information.

It is embedded with natural language processing and semantic analysis capabilities,

CLASSIFICATION WORKBENCH

An application that is used to create and analyze knowledge bases and decision plans. With Classification Workbench, you can also evaluate system performance by importing analysis data and viewing reports and graphical diagnostics.

KNOWLEDGE BASE

A single file encapsulating data that is required by the Classification Module for accurate content-based classification

DECISION PLAN

A collection of rules built in Classification Workbench that determine how the Classification Module classifies content items such as documents or e-mails. Each rule consists of one trigger and one or more actions.

CLASSIFICATION CENTER

A Web application provided with the IBM FileNet P8 integration that is used to manage the classification processes. You can use the Classification Center to determine the content to be classified, specify classification options (such as the decision plan to use and various runtime preferences), monitor classification activity, and view the classification results

Content Extractor

A command-line tool provided with the IBM FileNet P8 integration that is used to extract the content from an IBM FileNet P8 object store. You can import the extracted content into Classification Workbench and use it to train a knowledge base or provide test data for a decision plan.

It uses a properties file where option for what to be extracted is specified and extracts the document in XML format.

IBM WebSphere Transformation Extender (WTX)

2010-10-06T20:45:00.000-07:00

Its a dedicated data transformation engine for app integration. It’s being used in organizations around the world. A transformation engine accepts FILE docs or electronic messages as inputs, parsed them using data dictionary like definitions & transforms them into one or more o/p messages.

It can convert all most any formatted content and does this without any coding/scripting by developer. WTX is a family of products and has editions tailored to ESB, BPM and B2B products.

How does it connect to existing applications?

WTX has local file system support by default. This helps for testing transformations thoroughly before moving to the connectivity phase.

How does WTX aid application reuse?

For example Industry Standards, they get updated usually one/twice a year. As organizations are required to follow the standards so the rules are coded in to the apps. You can end up in spending so much time and money on maintenance and not on new projects. WTX protects apps from change and allow them to participate in new projects.

Making CXF Web service accept SOAP 1.2 request

2010-09-30T21:58:00.000-07:00

By default CXF Web Service provides SOAP 1.1 end point. In order for your web service to expose SOAP 1.2 endpoint and accept SOAP 1.2 request configure the following settings in server side CXF config file of the Web Service:

Creating SOAP 1.2 end point

<jaxws:endpoint id="auth" implementor="#AuthService" address="/cxfSearch12">

<jaxws:binding>

<soap:soapBinding version="1.2" mtomEnabled="true"/>jaxws:binding>

<jaxws:features>

jaxws:features>

<jaxws:inInterceptors>

jaxws:inInterceptors>

jaxws:endpoint>

Calling SSL enabled CXF Web Service From Java Client

2010-09-30T21:55:00.000-07:00

Calling a SSL enabled service which also expects UserToken to be passed can be very frustrating. It has been really painful for me to consume SSL enabled CXF service and I spent nearly 1 week to get it working.

Environment

Apache Tomcat 6.0.28

JDK 1.6

CXF 2.2.3

IBM Rational Developer 7.5.2

Spring Web 2.5.6

We deployed the CXF Web Service with SSL and installed the security certificate (self signed) on the client machine.

I was able to view the WSDL coming in the browser but the problem started when I tried to call Web Service from Java Client. I was getting “Message could not sent”. I set the proxy in RAD and imported the client certificate in the JVM. Configured following JVM arguments:

-Djavax.net.ssl.trustStore="C:\Program Files\IBM\SDP\jdk\bin\mykeystore"

-Djavax.net.ssl.trustStorePassword="password"

But this configuration did not change the error message.

My next attempt was to configure proxy arguments in addition to the above JVM arguments for my program

-Djavax.net.ssl.trustStore="C:\Program Files\IBM\SDP\jdk\bin\mykeystore"

-Djavax.net.ssl.trustStorePassword="password"

-Dhttp.proxyHost=yourproxy

-Dhttp.proxyPort=8080

-Dhttps.proxyHost=yourproxy

-Dhttps.proxyPort=8080

Now I started getting ‘SSLHandshakeException’, ‘javax.net.ssl.SSLHandshakeException: Couldn't find trusted certificate’ . It confirmed that the client was trying to use the certificate to reach Web Service but due to self signed certificate it was getting invalidated.

Then I found a link on internet which covered my problem scenario and suggested to accept whatever certificate your application is trying to use instead of JVM trying to validate it. I used following code to accept the certificate with out checking its validity and I was able to reach Web Service successfully.

import javax.net.ssl.TrustManager;

import javax.net.ssl.X509TrustManager;

import org.apache.cxf.configuration.jsse.TLSClientParameters;

import org.apache.cxf.endpoint.Client;

import org.apache.cxf.frontend.ClientProxy;

import org.apache.cxf.frontend.ClientProxyFactoryBean;

import org.apache.cxf.transport.http.HTTPConduit;

import org.springframework.context.ApplicationContext;

import org.springframework.context.support.ClassPathXmlApplicationContext;

public static void main(String[] args)

{

ApplicationContext context = new ClassPathXmlApplicationContext("appcontext.xml");

InfoService client = (InfoService) context.getBean("client");

ClientProxyFactoryBean factory = new ClientProxyFactoryBean();

Client proxy = ClientProxy.getClient( client );

HTTPConduit conduit = (HTTPConduit) proxy.getConduit();

TLSClientParameters tcp = new TLSClientParameters();

//Creating Trust Manager

TrustManager[] trustAllCerts = new TrustManager[] {

new X509TrustManager()

{

public java.security.cert.X509Certificate[] getAcceptedIssuers()

{

return null;

}

public void checkClientTrusted(

java.security.cert.X509Certificate[] certs, String authType) { }

public void checkServerTrusted(

java.security.cert.X509Certificate[] certs, String authType)

{

System.out.println("authType is " + authType);

System.out.println("cert issuers");

for (int i = 0; i < certs.length; i++) {

System.out.println("\t" + certs[i].getIssuerX500Principal().getName());

System.out.println("\t" + certs[i].getIssuerDN().getName());

}

};

tcp.setTrustManagers(trustAllCerts);

conduit.setTlsClientParameters( tcp );

client.callWebServiceMethod();

}

Resources used:

http://www.linux-support.com/cms/en/component/content/article/4-howtos/57603-custom-ssl-certificates-and-https-with-java-clients?directory=14

Read Posting from Daniel

http://www.java-forums.org/advanced-java/1307-java-security-cert-certificateexception-couldnt-find-trusted-certificate.html

http://mail-archives.apache.org/mod_mbox/cxf-users/200804.mbox/%3CAD43CBD88586D740B1CBFFB25336AB5218EF75@amer-ems1.IONAGLOBAL.COM%3E

http://blog.progs.be/?p=71

What is JaWin and how to use it?

2010-08-02T21:12:00.000-07:00

JaWin
The Java/Win32 integration project (Jawin) is a free, open source architecture for interoperation between Java and components exposed through Microsoft's Component Object Model (COM) or through Win32 Dynamic Link Libraries (DLLs).
For more information visit http://jawinproject.sourceforge.net/

How to use Jawin - A practical example
================================

a). If you have .tlb (COM Type Library) file available for the COM object you want to use then skip Step1 and proceed to Step3.
b). If you already have .Net component ready which you want to use from Java code then proceed to Step2:
c). If you want to develop a .NET component to be used via JAWIN then proceed to Step1:

Step1: Developing a .Net component (class library)

(a). Create an interface and before its declaration put .net attribute as given below
      [Guid("3823a63d-5891-3b4f-A460-DB0FB847075A")]
See the code snippet below for mor einformation:

using System;
using System.Collections.Generic;
using System.Text;
using System.Runtime.InteropServices;

namespace Org.Jawin.ManageWinProcess
{
       [Guid("3823a63d-5891-3b4f-A460-DB0FB847075A")]
       public interface IWinProcessOperations
       {
       Boolean IsProcessActive(String sProcessName);
       Boolean KillRunningProcess(String sProcessName);
}

b) Now Implement the interface created above and in the implementation class before the name of class declaration, type the following attributes
[Guid("25c2f5a2-1afe-36ce-BE27-84E040F5E19A")]
[ProgId("Jawin.WinProcessOps")] // You would be using this prog id while creating an instance of this class in JAVA.

See the code snippet below for more information:

using System;
using System.Collections.Generic;
using System.Text;
using System.ServiceProcess;
using System.Text.RegularExpressions;
using System.Runtime.InteropServices;
namespace Org.Jawin.ManageWinProcess
{

         [Guid("25c2f5a2-1afe-36ce-BE27-84E040F5E19A")]
         [ProgId("Jawin.WinProcessOps")]
         public class Operations:IWinProcessOperations
         {
             public Operations(){ }
             public Boolean isProcessActive(String ProcessName)
             {
                  String machine = ".";
                  Boolean processRunning = false;
                  // Get the current processes
                   System.Diagnostics.Process[] runningProcesses = System.Diagnostics.Process.GetProcesses(machine);
                 // Find those that match the specified regular expression
                  Regex processFilter = new Regex(ProcessName, RegexOptions.IgnoreCase);
                  foreach (System.Diagnostics.Process current in runningProcesses)
                   {
                    // Check for a match.
                     if (processFilter.IsMatch(current.ProcessName))
                       {
                           processRunning = true;
                           break;
                        }
                   }

              return processRunning;
             }

public Boolean KillRunningProcess(String ProcessName)
{
String machine = ".";
Boolean processKilled = false;
// Get the current processes
System.Diagnostics.Process[] runningProcesses = System.Diagnostics.Process.GetProcesses(machine);
// Find those that match the specified regular expression
Regex processFilter = new Regex(ProcessName, RegexOptions.IgnoreCase);

foreach (System.Diagnostics.Process current in runningProcesses)
{
// Check for a match.
if (processFilter.IsMatch(current.ProcessName))
{
   current.Kill();
   processKilled = true;
   break;
}
}
return processKilled;
}

public bool KillAndStartProcess(String ProcessName)
{
String machine = ".";
Boolean processKilled = false;
// Get the current processes
System.Diagnostics.Process[] runningProcesses = System.Diagnostics.Process.GetProcesses(machine);
// Find those that match the specified regular expression
Regex processFilter = new Regex(ProcessName, RegexOptions.IgnoreCase);
foreach (System.Diagnostics.Process current in runningProcesses)
{
// Check for a match.
if (processFilter.IsMatch(current.ProcessName))
{
   current.Kill();
   break;
}
}
System.Diagnostics.Process.Start(ProcessName);
return true;
}}}

Building .NET Library
In order to build the .Net Library code you have just written from the Visual Studio IDE, configure the settings as shown below:

Important: If this setting is not configured, build would generate a DLL but the TLB file generated using regasm on .net command prompt would create .tlb file which would not expose any method in JaWin browser. So this setting is crucial.

Step 2: Creating .tlb file for the .net component

You can create a tlb file for the .net component using Assembly Registration Tool in the Visual Studio command prompt.
Syntax : Regasm /tlb “dll path with dll name”

e.g : regasm /tlb “c:\winprocess.dll” (suppose name of our dll is winprocess.dll and it is available at c:\)

The above command would generate the corresponding .tlb file.

Step 3: How to use JAWIN BROWSER and create JAWIN stub for Java for COM

Download JaWin and extract its files in a directory. Suppose JaWin is available in c:\JaWin folder. Open command prompt and reach the ‘typeBrowser’ folder in Jawin directory.

C:\Jawin\jawin-2.0-alpha1\typebrowser

And then type
java -Xmx256M -jar jawinBrowser.jar

and hit Enter. [Note: Xmx256M in the above command allocates 256 MB RAM to this process]. It would then start the Applet as shown below:

Go to option ‘Project’ -> ‘New Project’ and type project name and then click on ‘New’ button as shown below:

Reach to your TLB file and when you are done, the contents of your tlb would be displayed as shown below:

Expand your interface (IwinProcessOperations in this case) and then select ‘Code Generation’->’Generate Selected Code’ and it would show the corresponding JAVA code under ‘Code’ tab as shown below:

Save this code as a JAVA class. Now you can import this class and use its methods in your code.
Note: Don’t try to modify this class file.

HOW to use JAWIN stub in java application

a). Include jaWin.jar in your build path and

b). Point to the path of jaWin.dll in run configuration by adding the following string under VM arguments(if running the code in eclipse or RAD)
-Djava.library.path="c:\JawinPath"

c). If you have .NET dll, put it in your project folder and register it using regasm command. If you are using pure COM dll then use regsvr32 command to register the COM component.

d). If you are using .net dll which was exposed as a COM then you would need to copy the .net dll in JDK\bin directory otherwise your program would not be able to find the object. This step is nor required if you are using pure COM. For more information visit http://jawinproject.sourceforge.net/jawinarchitecture.html

c). Import/add the Java class (JaWin stub) file created above in your application and then use it. The below snippets shows how to use this stub.

public static void main(String[] args)

{
boolean bResult;
IWinProcessOperations ops=null; //Jawin stub for the COM component
try
{
   //I have used Jawin.WinProcessOps because this was mentioned as a Prog id in the //class in .net.
   // You should use the prog id of your COM accordingly.
   ops = new IWinProcessOperations("Jawin.WinProcessOps");
   }

catch (COMException e1)
   {
    e1.printStackTrace();
    }
try
{
   bResult=ops.KillRunningProcess("WINWORD");
System.out.println("Process is active " + bResult);
}
catch (COMException e)
{
   e.printStackTrace();
}
}