Showing posts with label IBM Case Manager. Show all posts
Showing posts with label IBM Case Manager. Show all posts

Sunday 12 April 2015

JavaScript for Dynamic in-basket Filter (Case Manager Scipt)

//JavaScript for Dynamic in-basket Filter based on role and In-basket. 

Script: 

var um = parent.com.ibm.mashups.enabler.model.Factory.getUserModel();                                                        
var dfr = um.findCurrentUser();                                                         
var currentUserObj = dfr.start();                                                        
var currUser = currentUserObj.getDisplayName();                                         
var currRole =  ecmwdgt.getBean("spaceConfig").getEffectiveRole();                
fmsCurrInbasket = payload.currentInbasket ;
console.log('currUser = '+currUser+"  currRole="+currRole + "  Inbasket="+payload.currentInbasket);

if (currRole=='Employee' && payload.currentInbasket=='My Work')
 {
 console.log("inside Requestor if loop "); 
    console.log("Current User" + currUser);
 var filter= {                    
    "queueName":payload.queueName,                    
    "inbasketName":payload.currentInbasket,                    
    "hideFilterUI":false,                    
    "filters":[                               
  {                    
   "name": "EmpID",                    
   "value":currUser                     
  },     
  {                    
     "name": "Pointer",                    
     "value":'2'                     
  }
    ]                    
 };                    
    console.log("inside loop: " +filter);               
    return filter;
 }
 
return payload;
   
Wiring:

 



Monday 16 February 2015

IBM Case Manager Solution Deployment (Exporting and Importing)

IBM Case Manager Solution Deployment (Exporting and Importing) through Commends 

Deploying solution from one system to another system 

(Example : Dev -> UAT or Dev -> Prod )
  

1. Export Solution (Ex: Dev): The exportSolution command exports a case management solution or solution template from the development environment domain before you move the solution to another environment.

Syntax: 

configmgr_cl exportSolution -profile myprofile 
 -solutionName solution_name | -solutionTemplateName template_name 
 -solutionPackage package_file

Example: 

Unix or AIX: 

1st step:  Change current directory

cd /installed path/CaseManagement/configure/

2nd Step: Execute below export command 

configmgr_cl exportSolution -profile Dev123 -solutionName "Sample" -solutionPackage "/opt/Solutions/Soultion_16Feb15.zip" 

Windows:

1st step: Change Current directory

cd C:\Program Files\IBM\CaseManagement\configure\

2nd Step: Execute below export command

configmgr_cl exportSolution -profile Dev123 -solutionName "Sample" -solutionPackage "C:\Solutions\Soultion_16Feb15.zip" 

  • Sample is a solution name
  • Dev123 is a profile name (The full path to the profile directory, such as "C:\Program Files\IBM\CaseManagement\configure\profiles\Dev123" (For Windows) or "/opt/IBM/CaseManagement/configure/profiles/Dev123"(For UNIX or AIX)).
  • "C:\Solutions\Soultion_16Feb15.zip" and "/opt/Solutions/Soultion_16Feb15.zip"  are
    Specify the full path and file name for the exported solution package ZIP file. If the path includes spaces, put the entire path in double quotation marks.

2. Copying (Dev  to UAT or Prod): After Export the solution Soultion_16Feb15.zip file is created in Dev, need to copy the above zip file in Prod or UAT

3. Import Solution (UAT or Prod): The importSolution command imports a case management solution or solution template package into another environment.

Syntax: 

 configmgr_cl importSolution -profile myprofile -projectAreaName project_area_name -solutionPackage package_file


Example: 

Unix or AIX: 

1st step:  Change current directory

cd /installed path/CaseManagement/configure/

2nd Step: Execute below export command 

configmgr_cl importSolution -profile myDevelop1 -solutionPackage "/opt/Solutions/Soultion_16Feb15.zip"
 
(or)

 configmgr_cl importSolution -profile myDevelop1 -projectAreaName prodProjectArea -solutionPackage "/opt/Solutions/Soultion_16Feb15.zip

Windows:

1st step: Change Current directory

cd C:\Program Files\IBM\CaseManagement\configure\

2nd Step: Execute below export command


configmgr_cl importSolution -profile myDevelop1 -solutionPackage "C:\Solutions\Soultion_16Feb15.zip"
 
(or)

 configmgr_cl importSolution -profile myDevelop1 -projectAreaName prodProjectArea -solutionPackage "C:\Solutions\Soultion_16Feb15.zip"

  • prodProjectArea is Specifies the name of the project area for the solution. This option is valid only for importing a solution package to into another development environment
  • myDevelop1 is a profile name (The full path to the profile directory, such as "C:\Program Files\IBM\CaseManagement\configure\profiles\Dev123" (For Windows) or "/opt/IBM/CaseManagement/configure/profiles/Dev123"(For UNIX or AIX)).
  • "C:\Solutions\Soultion_16Feb15.zip" and "/opt/Solutions/Soultion_16Feb15.zip"  are
    Specify the full path and file name for the exported solution package ZIP file. If the path includes spaces, put the entire path in double quotation marks