Configure Database Connection Alias in Process Configuration Console(PCC) (For DbExecute step)

Configure Database Connection Alias in Process Configuration Console(PCC) (DbExecute system step)


1. Log on to Workplace XT
2. Go to Tools --> Administration --> Open Process Configuration Console


 

3. Right Click on Isolated Region open properties
4. Open DbExecute Connections tab



5. Click on Add button

 



6. Enter Name and Select Database Type (DB2 or MS-SQL or ORACLE)




7. Enter remaining Database details (Database Name, Database Host, Database Port, Database User and Database Password)

 

8. Click on ok.

****Database Connection Alias created Successfully ****

10. Use the above db execute alias in DbExecute system function to run a stored procedure in a specified database.


 

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

Create a Document with Content (CE API)

Create a Document with Content (CE API)
-----------------------------------------------------------

//Get CE Connetcion
//Create Subject
//Push Subject

//Get Domain (domain)
ObjectStore os = null;
objectStoreName = "COS"
os = Factory.ObjectStore.fetchInstance(domain, objectStoreName, null); 


 //Get Folder
 Folder folder=null;
 folderName = ''/Sample";
folder=Factory.Folder.fetchInstance(os, folderName, null); 


 //Get the File details
InputStream file = "";
String fileName = "";
int fileSize = "";
 
// Create Document

String docClass = "dcumnet class name";
Document doc = Factory.Document.createInstance(os, docClass); 
if (file != null && fileSize > 0) {
                        ContentTransfer contentTransfer = Factory.ContentTransfer.createInstance();
                        contentTransfer.setCaptureSource(file);
                        contentElementList.add(contentTransfer);
                        doc.set_ContentElements(contentElementList);
                        contentTransfer.set_RetrievalName(fileName);                       
                        doc.set_MimeType(getMimetype(fileName));
                    }
                   

//Check-in the doc
doc.checkin(AutoClassify.DO_NOT_AUTO_CLASSIFY,CheckinType.MAJOR_VERSION);                   
//Get and put the doc properties
String documentName =""
Properties p = doc.getProperties();
p.putValue("DocumentTitle","abcd");
p.putValue("Name","Rakesh");
p.putValue("Number","01234"); 
              

doc.save(RefreshMode.REFRESH);

//Stores above content to the folder

 ReferentialContainmentRelationship rc = folder.file(doc,
                                    AutoUniqueName.AUTO_UNIQUE,
                                    documentName,
                                    DefineSecurityParentage.DO_NOT_DEFINE_SECURITY_PARENTAGE);
 rc.save(RefreshMode.REFRESH);




 

Security to Objects

Normally, an object's security is controlled or determined in four ways. (Markings, if they are used, would be a fifth way)

1. Security parent and inheritance: Permissions can also be inherited from a parent object. Inheritance can take place between a class and its subclass, and between a folder and its containable objects (documents, custom objects, and other folders).
    
2. Direct Security: Users who have sufficient permission can edit an object's security by directly adding or removing security principals, or by changing the existing permissions already granted.
    
3. Default Instance Security : As an integral part of the class and instance design, objects such as documents, folders, and events are instances of their class. The class includes, among other things, a property containing the default security permissions that will be applied to all instances of the class. This is the simplest method of applying security: the security design sets up the default security that all instances of a class should have, and then all objects based on that class will have the same default security.
    
4. Security Policy and security templates : Security policies contain security templates which let you automatically apply security to documents, folders, and custom objects. In the case of documents, security templates can be associated with one of the several versioning states that documents pass through (Released, Superseded, In Process, or Reservation). This powerful feature provides efficient application of fine-tuned security across many objects.
    
5. Marking Sets : FileNet Content Engine (CE) Markings or Marking Sets provides a way to define a level of security on objects (i.e. documents) in addition to the normal FileNet P8 object security model. By using markings, access to objects can be controlled based on specific property value. Marking set's are collection of CE objects known as marking objects. Marking sets allows setting up security on an object with means of property template. When a marking is applied to an object, the resulting access permissions for the object are a combination of the settings of its original access permissions (through ACL) and the settings of the markings 'Constraint Mask' for each marking that is applied to it. The result of this combination is the effective security mask.