Serverless Architecture

Serverless Architecture

What is Serverless Architecture

Serverless do require servers but the servers will be managed by Vendor. We need not worry about the infrastructure and its maintenance. This is a one step forward to PaaS (Platform as a Service) which is called as FaaS (Function as a Service) or BaaS (Backend as a Service).

Pros:

• Cost efficient - The provider charges for resources utilized not for the server instance
• Less time to market
• The focus should be on functionality development, not the infrastructure

Cons: 

• Not suited for high-performance computing
• Cryptojacker's paradise
• DoS your self
• Startup latency (cold start)

Major Service Providers:

• AWS Lambda                - Node.js, Java, C#, Python and Go
• Google Cloud Functions  - Node.js
• IBM OpenWhisk             - Node.js, Java, Python, Swift
• Microsoft                       - Node.js, Java, Python

CSS3 animations

Animation using CSS3

CSS3 supports animations. Below I have few samples for CSS3 animations.

Sample 1: Color changing button

CSS:

.ccbtn { 
                  width: 100px; 
                  height: 30px; 
                  background-color: red; 
                  border-radius:20px; 
                  position: relative; 
                  animation-name: example; 
                  animation-duration: 10s; 
                  animation-iteration-count: infinite; 
}

@keyframes example { 
                  0% {background-color:blue; } 
                  25% {background-color:cyan; } 
                  50% {background-color:yellow; } 
                  75% {background-color:red; } 
                  100% {background-color:green; } 
}

<div class="ccbtn"></div>

Sample 2: Animation

CSS:

.ball {
            width: 30px;
            height: 30px;
            border-radius:20px;
            background-color: blue;
            position: relative;
            animation-name: example2;
            animation-duration: 5s;
            animation-iteration-count: 1;
 }

.rock{
             width:300px;
             height:100px;
             background-color:brown;
             border-radius: 0px 10px 0px 0px;
}

@keyframes example2 {
             0%   {left:0px; top:0px;}
             75%  {left:290px; top:0px;}    
             100% {left:300px; top:100px;}
}

<div class="ball"></div>

<div class="rock"> </div>

Rounded Corner Buttons using CSS3

Rounded Corner Buttons using CSS3

There are loads of useful features available in CSS3. Curved edge button is one of the valuable features. Using border-radius attribute we can style the buttons with curved edges. Previously images are used for curved edge button but with new CSS3 we can easily create the curvy edges.

Sample:

CSS for the button:

input{

                     clear:both;

                     width: 100px;

                     height: 30px;

                     border-radius: 20px 20px;

                     background-color:#42b0f4;

                  }

We can create different shapes based on our requirements. We can define the border-radius for the four edges. If we are defining four values then, the top left edge is denoted with the first value and then clockwise edges for the remaining.

CSS for the button:

input{

                     clear:both;

                     width: 100px;

                     height: 30px;

                     border-radius: 20px 0px;

                     background-color:#42b0f4;

                  }

CSS for the button:

input{

                     clear:both;

                     width: 100px;

                     height: 30px;

                     border-radius: 20px 20px 5px 5px;

                     background-color:#42b0f4;

                  }

Opentext Enterprise Connect

OpenText Enterprise Connect

OpenText Enterprise Connect is a desktop interface to allowing the user to interact with the OpenText Content Suite directly from applications such as Microsoft Office and Adobe Acrobat

OpenText Enterprise Connect is similar to MS Office integration in  FileNet.

OpenText Enterprise Connect supports integrations with

• MS Office Suite
• MS Outlook
• Adobe Acrobat
• Windows Explorer
• IBM Lotus Notes
• MS Office 365 Desktop Professional

Opentext Brava for Content Suite

OpenText Brava For ContentSuite

Brava! provides access to content in virtually any format without allowing the source file to be edited or downloaded. It enables workers to view the content they need and collaborate with coworkers and external stakeholders all within the business rules so organizations can operate efficiently while meeting compliance and security objectives.

Brava having out of the box integrations with 

• Sharepoint
• OpenText Content Suite
• OpenText Documentum Webtop & D2
• IBM FileNet
• IBM Content Navigator

 Features:

• Universal Viewing
• Secure File Publishing (TIFF, PDF, CSF) 
• Document Redaction
• E-Signature
• Document Annotation

 3D Support Features (Additional Licensing):

• Rotate and zoom
• Explode Assemblies
• View Cross sections
• Take Measurements
• Locate Parts
• Browse Part Information
• Share Views

Plase check the link for Brava supported file formats

Opentext Imaging Enterprise Scan

OpenText Imaging Enterprise Scan

OpenText Imaging Enterprise Scan converts the hard copy documents to digital images. It will capture and index from Scanners, FAX, Email, Shared drive and mobile.

OpenText Imaging Enterprise Scan Features:

• Batch Scanning
• Ad-hoc Scanning
• Barcode Scanning
• Web Interface for distributed scanning
• Mobile Capture
• Automatic Document Separation
• Document Enhancement
• JScript.NET to extend the functionality

OpenText Imaging Enterprise Scan Source :

• FAX via Microsoft Office/Lotus Notes
• Email
• Shared Drive/Folder

OpenText Imaging Enterprise Scan Output Formats:

• TIFF
• PDF
• Searchable PDF
• PDF/A-1b

Opentext Content Server

OpenText Content Server

OpenText Content Server is the core content repository and foundational document management technology for the OpenText Enterprise Content Suite.

Content Server Features: 

• Document Management
• Smart UI
• Perspective Manager
• Search
• Content Filters
• Document Thumbnails
• Office Editor
• Workflows
• Social & Collaborative Capabilities
• Forms
• Content Reporting
• Content Suite Viewer 

Content Server Development Tools:

• RESTful API
• Content Server Widgets
• AppWorks

Opentext Content Suite Components

OpenText Content Suite Platform

OpenText Content Suite Platform, the foundation for OpenText Enterprise Information Management (EIM) offerings, is a comprehensive enterprise content management (ECM) system designed to manage the flow of information from capture through archiving and disposition.  

OpenText Content Suite comes with the below components

1. Content Server
2. Records Management
3. Enterprise Connect
4. Archive Center
5. Imaging Enterprise Scan
6. Tempo Box

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.