Friday, June 1, 2018

Restarting WAS ND


Restarting WebSphere Application Server Network Deployment Edition

Websphere Application Server Network Deployment edition contains more than one node to manage. Deployment manager is used to managing the nodes. 

To restart the WAS ND we need to follow the below sequence. The below shell scripts are used in Unix/Linux. For windows, we can use the .bat files.

Make sure that you login using the admin credentials. To run the shell scripts you need admin privileges.

  • stop servers using WAS Console. 
    • Login to WAS Console
    • On the left menu click on servers link
    • Select all the servers and click on the stop button
  • stop node agents using stopNode.sh command
    • Go to <WAS Profiles dir>/<node>/bin
    • run the command ./stopNode.sh 
  • stop DMGR using stopManager.sh
    • Go to <WAS Profiles dir>/dmgr/bin
    • run the command ./stopManager.sh
  • start DMGR using startManager.sh
    • Go to <WAS Profiles dir>/dmgr/bin
    • run the command ./startManager.sh
  • start node agents using startNode.sh
    • Go to <WAS Profiles dir>/<node>/bin
    • run the command ./startNode.sh
  • start servers using WAS Console
    • Login to WAS Console
    • On the left menu click on servers link
    • Select all the servers and click on the start button


FileNet Platform upgrade from v5.1 to v5.2.1

FileNet Content Engine Upgrade From v5.1 to v5.2.1

Recently I got an opportunity to work on FileNet upgrade. We have upgraded FileNet P8 v5.1 to v5.2.1. I would like to share my experience.


FileNet Environment Details:

Unix, SQL Server, AD, WAS ND


FileNet Upgrade Approach:

There are two ways to implement the upgrade
  1.  In-place upgrade
  2. Clone & upgrade

We have chosen the clone & upgrade path.

Pros:
  • It will not disturb the existing setup
Cons:
  • Need to spend more on infrastructure
  • Need to spend more efforts in cloning the environment

FileNet Upgrade Execution:

We can divide the tasks into.

1. Cloning the environment -
  • Copy the CE, PE and AE folders 
  • Copy the CE, PE databases 
  • Configure and deploy the applications
  • For PE need to change the pointers from a source server to a destination server

2. Verify the cloned environment

  • start the CE, PE and AE
  • Check the functionality is working as expected

3. Install the FileNet v5.2.1

  • Follow the installation instructions and install the 5.2.1 on the destination server
  • Configure and deploy the CE

4. Upgrade Content Engine

  • Upon starting the CE the platform will run the auto-upgrade tool
  • The progress is monitored using   http://server_name:port/FileNet/AutomaticUpgradeStatus 

5. upgrade Process Engine

  • IBM provided peupgrade tool for PE upgrade. 
  • Prepare the PE databases for upgrade
  • Open the tool and provide the details.
  • Run the tool. PE upgrade will take a while compared to CE upgrade.

Friday, March 9, 2018

IBM FileNet CPE v5.5 released

IBM FileNet CPE v5.5 Release Notes

IBM Recently released the new version of the FileNet Content Engine Platform v5.5.

The new features are
  • The following components, which were deprecated, are no longer supported in this version:
    • IBM FileNet Workplace XT
    • Application Engine
    • Workplace
    • IBM FileNet Integration for Microsoft Office
    • IBM FileNet Connector for Microsoft SharePoint Web Parts
  • Web-Services Reliable Messaging (WS-RM), UDDI and WSSR as service registry for Process Orchestration (Web Service invocation), stand-alone legacy Component Manager, and Java Database Connectivity (JDBC) provider support are deprecated in this release.
  • The Content Platform Engine S3 connector provides the ability to store and retrieve documents to and from an S3-compatible object storage solution that is deployed either on premise or in a private or public cloud.
  • Class Designer and Application Designer access to Administration Console for Content Platform Engine
  • Use token groups for Windows Active Directory
  • Role based access to objects
  • LDAP single entity lookup behavior to remove duplicates when using multiple LDAPS configured
  • FileNet Deployment manager supports the below object types
    • User-defined RecoveryBin subclasses
    • User-defined Hold subclasses
    • Sweep jobs
  • This release includes long list of new classes and properties.
  • JBoss Application Server is no longer supported.
  • The Composite Platform Installation Tool for installing a single server of FileNet P8 Platform is no longer supported.
  • A local installation of the documentation is no longer supported.
  • The following platforms are no longer supported:
    • HP and HPUX operating systems
    • Solaris operating systems

    Wednesday, March 22, 2017

    Display List Of Websphere Servers using Jython script


    To display the list of servers in Websphere Application Server Jython is using AdminTask object.

    The AdminTask,listServers will list down the servers. The server type is the parameter passed to list down different types of servers.

    To list the Websphere Application Servers
    AdminTask.listServers('[-serverType APPLICATION_SERVER]')

    To list the Websphere Web Servers
    AdminTask.listServers('[-serverType WEB_SERVER]')

    To list the Websphere Proxy Servers
    AdminTask.listServers('[-serverType PROXY_SERVER]')

    To list the Websphere Liberty Servers
    AdminTask.listServers('[-serverType LIBERTY_SERVER]')

    To list the Websphere on-demand routers
    AdminTask.listServers('[-serverType ONDEMAND_ROUTER]')

    To list the Websphere PHP servers
    AdminTask.listServers('[-serverType PHP_SERVER]')







    Saturday, October 20, 2012

    Introduction to IBM Datacap

    Recently I had an opportunity to work on the IBM Datacap. Datacap is a good document capturing tool and is acquired by IBM in 2010. I have used the Datacap Taskmaster Capture product and the version is 8.0. Recently IBM released the version 8.1 of Datacap Taskmaster Capture.

    Previously I have worked on the IBM FileNet Capture so it is very natural that I will start comparing the Datacap features with FileNet Capture when I start working on this product. In the first look Datacap seems to be more complex than the FileNet capture and it requires a steep learning curve. I can say that the Datacap is a framework rather than a tool as it is flexible enough to extend the functionality.
    At a very high level, the advantages of Datacap over FileNet capture are
    • Datacap having the web client so it is a true distribution capture tool
    • Datacap having inbuilt data recognition capabilities where in FileNet capture we need to use ADR for recognition
    • Datacap is flexible enough to integrate with repositories other than FileNet 
    From architecture point of view Datacap is very flexible. It offers a vast set of predefined methods in the actions library and most of the scenarios these predefined methods are enough to fulfill the project requirements. These actions library items called as rules are grouped to form the rule sets and these rule sets are grouped together to form the task. All these tasks are grouped together to complete the job. So developer having the fine control over every action as the tasks are developed using the rules and these rules are set by the developer. Remember that the rules are executed in the order so it is important to set the order of the rules.

    The troubleshooting also simple as it provide the logs for each task but I fell that the detailed exception logs are missing. The log data, images and other application data will be saved to configured physical drive. The Datacap Studio tool provides the option to debug the rule sets and debugging process also very simple.


    IBM Datacap comes along with MS Access database and developer having the option to configure with Oracle or SQL Server. The installation process is very simple and doesn't take much time. IBM Datacap comes with sample projects and developers can use these projects as a reference.



    Monday, January 16, 2012

    Updating the mime type property of the doucments in Filenet

    When we need to update the properties of the large number of documents  in Content Engine, Filenet provides the script execution option for bulk updates. The scripts are executed using Filenet Enterprise Manager. This option is provided in the search functionality so that we can search the documents based on conditions and update only those articles. This makes developer or support engineer job is easy. Custom property updates generally doesn't require the checkout and checkin of the documents. We can directly update the properties using the script. We can use the below code to update the property.

    CEObject.Properties("DocumentType").Value="Confidential"
    CEObject.Save

    When I tried the above code to update the mime type property it is not working and I found out that it is a read only property and to update the read only properties like mime type we need to checkout the document and before checkin the document we need to update the property. So I have updated the above scrip as mentioned below.

    CEObject.Checkout
    CEObject.Reservation.Properties("mimetype").Value= "text/html"
    CEObject.Reservation.Save
    CEObject.Reservation.Checkin

    After executing the above script I have observed that the mime type property updated as expected and document version also upgraded but the content of the document is missing. While checkin the document we need to pass the content otherwise it will save the empty document. So I have written a script to get the document content and saved to the local folder and while check-in the document i have added the content. 


    CEObject.CopyContent "file:///localfoldername/filename"  
    CEObject.Checkout      
    CEobject.Reservation.Properties("MimeType")= "text/html"   
    CEObject.Reservation.Checkin "foldername\filename"




    The above code is used to checkout the content and saved to the local folder and update the mime type property and checkin the content from local folder.

     












    Tuesday, December 13, 2011

    Bulk updates in FileNet

    Bulk Updates in FileNet using FEM

    Bulk updates are used in FileNet when there is a requirement to update a property of a large number of documents with the similar data. Suppose there is a requirement to update Document Type property of a particular document class as the document type values are revisited and updated, in this case, we can use the bulk update to update the document type property of the documents to a specified value.

    Bulk update functionality is performed using FEM(FileNet Enterprise Manager) and either VBScript or JScript is used as a scripting language. In the FEM search window using the script tab we can execute this bulk update. In the script, tab check the Execute Script check box to enable the script area

    to perform the property update use the below VBScript code

    CEObject.properties.item("DocumentType").vlaue = "NewDocuemntType"
    CEObject.save

    The above code is good at updating the single value properties but to update the multi-value properties we need to modify the code as below


    CEObject.properties.item("multivaluePropertyName").value.add("newPropertyValue")
    CEObject.properties.item("multivaluePropertyName").value.remove("oldPropertyValue")
    CEObject.save




    How to find the WAS Console Port number

    In WAS Server go to the below path <WebSphere Installation Path>/Profiles/<Dmgr profile name>/logs Check for " AboutTh...