Do the following to generate a SOAP service.


1) Define your input, output and fault output in an xsd schema.

2) Create a subprocess which contains either the input and output as the start and end respectively orinput and output/fault in your start and end of your subprocess.

3) right click over your subprocess or if you have multiple subprocesses you want to turn into SOAPservices place them all into a folder and right click over the folder and there should be an option at thebottom that says “Tools or Multi-User” > “Generate Webservice” .

Once you create this service you should look into using an “http receiver” and “http response” activitywith the “SOAP retrieve resource” activity to allow people to get your wsdl from your service.

Once you do that you can use Axis or a Tibco BW Webservice client using the “SOAP Request Reply”activity to draw your wsdl automatically from your soap service.




For training on TIBCO BusinessWorks mail us at [email protected]

REVISION 0.1:
Change 1:
The following changes have been made to the ParseAndTransform process.
- Add 2 output parameter to the process. They are configured as the input parameter of the ‘End’ activity of the process.
> empColl – This element contains a copy of the empAccumulator process variable
> outputFileName – This element contains the output filename to be used by the downstream file writer activity. The reason behind this design decision is that when a new data model output is required, a new sub-process will be created by the developer and deployed into the BW engine. Different ParseAndTransfor process responsible to produce different data model based on different xsd will cause a different XML file name to be written by the downstream writer activity.

Example: ParseAndTransform sub-process will have its output writen to a file called ConsumerXXX-UniqueID.xml. ParseAndTransform will have its output written to a file called ConsumerYYY-UniqueID.xml. These output filename will eventually be published to interested parties.

Change 2:
EmployeeDataFormat (Data Format) has been updated to contain ‘Complex Element’ rather than ‘XML Element Reference’ to demonstrate the difference between the data model of the original input file and the desired out file (employees xsd). The Data Format defines the CSV file to contain the following fields

lastname,fistname,empNum,hireDate,department,manager

——————————————————————-

Been busy with work and done heaps of catch up with the TIBCO SOA platform. Came back from the TIBCO NOW seminar in Melbourne and got a good picture of what to expect from TIBCO product roadmap. I have to say TIBCO’s platform is nimble. They really know how to do integration and have learned a lot from their customers in specific verticals. But that is from a helicopter view. OK, let’s start.
This article is a part of the series of articles target to describe crude ‘reference implementation’ of File Gateway pattern in the book “SOA Design Patterns” by Thomas Erl.

This article explains the steps to create a file gateway that perform the following tasks.

1) A legacy system writes a batch flat-file into an inbound folder
2) The parser-transformer component polls and retrieve the flat file
3) The parser-transformer parses the data and performs data format transformation
4) The parser-transformer optionally performs data model transformation
5) The parser-transformer writes file to an outbound folder
6) The parser-transformer optionally broadcasts/triggers an event that a file is ready for consumption

The final product
Due to the width and depth covered in this topic, this article is split into 4 parts. The first part talks about how to create a TIBCO-BW process definition to parse and transform data models.
In the second part we will be extending the parser-transformer process to write the resultant file into the outbound folder. We will also implement four more global variables to enable configuration of inbound file path, outbound file path, semaphore file extension as well as the file pattern to watch.
The third part of this article will describe the steps to create a simple file poller process and invocation of the parser-transformer process.
The fourth part of this article will look at testing and deployment of this gateway into the TIBCO BW infrastructure, some performance tuning and monitoring using TIBCO Hawk agents.
In the roadmap, one would hope to have/be able to interact with the following capabilities:

1) Publish transformation completion events to the interested parties (typically the consumers, can also be the legacy providers provided they are capable of listening to events)
2) Pluggable architecture of schema specific parsers/transformation engines, effectively supporting one source multiple target use.
3) Load balancing via TIBCO infrastructures
4) Service call-back (pattern)
5) Protocol bridging (pattern)
6) Schema Centralisation (pattern)
We will discuss the appropriateness of item 4, 5 & 6 when time permits.
The writing of this article is unrehearsed. It may and will contain errors and inaccuracies, both technically and organisationally. Your comments and corrections are very welcomed.
Here goes the first part.
Begin with the ends in mind…here is what we will get at the end of this article.

The inbound folder is for incoming files, usually file dumps performed by the legacy system. Corresponding semaphore files will also transiently exist in this folder.
The outbound folder, on the other hand, holds the parsed and transformed files for the targeted consumers.
2) Create a XML schema that defines the data structure to be handled by the parser/transformer process. We created the schema using Oracle JDeveloper, based on the EMP table from the SCOTT schema. I have to admit that this tool, like many other commercial XML tools, provides better user experience through the adoption of widely accepted visual paradigm.

3) Create a new TIBCO Designer project.
Launch the TIBCO Designer. Create a new empty project, name it as FileGateway.

5) Import the schema of the data model output expected from this process. This schema will be referenced multiple times throughout the entire process definition. Notably in the definition of Data Format, Parse Data and other activities.
To import the schema we have created in Step 2, make sure the ParseAndTransform folder is selected. Under the Project menu, select ‘Import Resources from File, Folder, URL…’.

In the ‘Import Resource of File…’ dialogue box, select the ‘File (.xsd, .xslt, .wsdl, .*)’ as the Format.

In the ‘File:’ field, click on the binocular icon to browse for your schema file. Our file is named employees.xsd.
You should now have a schema appearing on the Designer Panel.

6) Our parser will need to know how to parse the CSV. This step involve the process of defining an activity call ‘Data Format’. Just as one would do when importing a CSV file into MS Excel, we will define the format, the delimiter character, the EOL character and other characteristic of the input flat file.
Back to the ParseAndTransform folder, in the Designer Panel, right-click and select ‘Add Resource’ à Parse à ‘Data Format’ sub-menu item.

In the configuration panel, click on the ‘Data Format’ tab, we will specify the content type as ‘Complex Element’.
Click on the ‘+’ button, a default ‘root’ element will be added. Rename it to ‘emp’. Define the children elements as shown in the picture below.

Click the ‘Apply’ button to commit your changes.
Before we process further, let’s look at what we have done.
We have
- Created a XML schema using our preferred XML authoring tool. We called that schema ‘employees.xsd’. It contains 2 complex types and 2 elements.
- Created an empty TIBCO Designer project called FileGateway.
- Create a new folder called ParseAndTransform in the FileGateway project.
- Imported the ‘employees.xsd’ schema into the ParseAndTransform folder
- Created a Data Format that references the employees.xsd, we called this Data Format ‘EmployeeDataFormat’.
In the next step we will create a process definition that will perform the following tasks.
- Takes an input that contains filename information from an external process.
- Parses the inbound file (Parse Data activity)
- Constructs the employees collection from the parsed records (Mapper activity)
- Updates a process variable that acts as accumulator (Assign activity)
This process definition will be built with the following capabilities:
- Configurable number of records to be grouped for resource optimisation/tuning

7) Add a new process under the ParseAndTransform folder.
Click on the ParseAndTransform node on the Project Panel. One the Designer Panel, right click and select the Process à Process Definition sub-menu item.

Define a process variable to act as an accumulator of employee records.

8) Up to this stage, we have an empty process definition. This process will not poll the file system, the polling part will be performed by the parent process, or even a separate component, depends on our design; instead, this process takes an input that specifies the fully qualified filename to be parsed. In this step, we need to specify the input parameter, and we will define this at the ‘Start’ activity of the process definition.
Double click on the ParseAndTransform process definition icon in the Designer Panel.

Click on the ‘Start’ activity icon, in the Configuration Panel, click on the ‘Output Editor’ tab.
Click the ‘+’ sign under the ‘Output Editor’ tab and name that parameter as ‘inboundFileName’. Specify the Content as ‘Element of Type’ and the Type as ‘String’. Click the ‘Apply’ button to make the changes effective.
Note: This tab is called ‘Output Editor’ because it allows one to specify the output that will be available to all downstream activities. This ‘output’ parameter will appear as ‘input’ parameter when the entire process is reference from another activity or process. We will see how this works in the coming steps.

9) Define a global variable called CHUNK_SIZE of type integer. This variable will be referenced in the ‘Group’ for grouping of records for processing. This value of this variable can be configured in the TIBCO Administrator console during the deployment and possibly would be useful for performance turning.
To define a global variable, click on the Global Variables panel. Click on the pencil icon to open the Advanced Editor. Click the ‘abc’ icon at the bottom of the Global Variables pop-up window and name that variable as ‘CHUNK_SIZE’ of type Integer. Assign it a default value of ‘3’.

We shall see the newly created variable appear in the Global Variables list together with other pre-defined variables.

10) Add the necessary activities into the process definition.
Add the ‘Parse Data’ activity.
Double click on the ParseAndTransform process definition, in the Designer Panel, right-click on the white space area to insert a Parse Data activity.

Click OK. When back to the configuration tab, ensure the ‘Input Type’ field is specified as ‘File’. Click ‘Apply’ and save the project.

11) Wire the ‘Start’ and ‘ParseEmpsCSV’ activities together.
Right click on the ‘Start’ activity to select ‘Create Single Transition’ menu item. Note that the cursor pointer changes to a hairline ‘+’.

Click OK. In the Input Type, select ‘File’ from the dropdown box.

Click on the input tab, map the input fields with the required process data. Two values are required. The first one, is the filename which will be mapped to the ‘inboundFileName’ of the Start activity. The second input, noOfRecords, will be mapped to the CHUNK_SIZE defined as the process variable earlier.

Enter a literal 0 into the SkipHeaderCharacters field as out CSV file starts from the first column.
The next activity in the process will be the Mapper activity. This activity in our process will perform 2 functions. First, it acts as a mapper to map the output of the Parse Data activity into the final form. The second function which is equally important is that it will perform the ‘accumulation’ of the employee records in every iteration of the group (will be discussed later) it operates in.

12) Add a Mapper activity, name it as BuildEmpsColl.
Right click on the Designer Panel to add a Mapper activity located under ‘General Activities’ menu.

Create a transition from ParseEmpsCSV into BuildEmpsColl.
In the input editor tab, define the input parameter that this activity will take.

In the input tab, we need to map 2 inputs from the process data into one employee collection. One of the process data is the output of ParseEmpsCSV activity, the other is the empAccumulator process variable. Parsed result from every iteration will be accumulated in empAccumulator process variable.
Right click on the emp element in the Activity Input pane and select ‘Duplicate

To map the process data, expand $empAccumulator in the process data pane and drag the child node (empColl) into the first copy of emp in the Activity Input pane.

In the dialogue box, select ‘Make a copy of each ‘emp’

Repeat the same for the output of ParseEmpsCSV activity.

In the dialogue box, select the ‘For each…’ option.

Click the ‘Next’ button.

Mapper is a powerful activity that can perform many transformation tasks. In the above example, the incoming CSV file contains 2 columns for a name, i.e. first name and last name. The output file (the xsd schema) has only one element called ename, so we need to concat the fields into one. This of course depends on the requirement. Refer to the TIBCO documentation for more details and examples.
Now we need to update the accumulator with this new value. We use the ‘Assign’ activity for that.

13) Add a ‘Assign’ activity to the process. Assign activity is under the ‘General Activities’ palette. Name the activity ‘UpdateProcessVar’. The process variable to update is empAccumulator. Create the required transition, including the one that transition to the ‘End’ activity.
In the input tab, map the entire empColl into the process variable.

When asked, just specify “select ‘Make a copy of each ‘empColl’”.
Up to now, our process definition looks like this.

We are getting there. The next step is to wrap all the activities into a group so that iteration can be performed based on group of records. This approach is optional, but will become visibly important when the file size being processed is large, such as 1GB or even 2GB.

14) Group the activities. Select the activities that we want to group. ParseEmpsCSV, BuildEmpsColl and UpdateProcessVar. Multi select can be performed by holding down the control key while selecting. Click the ‘Create a group’ icon on the tool bar.

15) Configure the group. Select the created group, in the configuration tab, select ‘Repeat-Until-True’ as the group action. Enter ‘i’ as the index name and use the following XPath expression as the condition to stop the iteration.
                                                               $ParseEmpsCSV/Output/EOF = string((true()))
The expression will cause the iteration to exit when the parser (ParseEmpsCSV) encounters the EOF character in the input file.

16) Define the process output at the ‘End’ activity.
Click on the ‘End’ activity. In the ‘Input Editor’ tab, add the following elements under a default root schema called ‘group’. You can choose other name for this root schema, I would just accept the default name ‘group’.

In the ‘Input’ tab, drag the $empAccumulator process variable into the empColl element in the Activity Input pane. This will be out process output. This output will be used by the downstream writer to create the XML file.
Paste the following XPath formula into the ‘outputFileName’ element.
                       concat('EMP-OUT00A-', tib:format-dateTime('yyyyMMdd-HH-mm-ss', current-dateTime()),".XML")
The first part of the output filename is hardcoded for the sake of simplicity. This is not critical as the filename convention is specific to this particular implementation of ParseAndTransform process.

Developing a process that will read and send an image in an e-mail. This image is a folder within this process.

Solution :
If your images exist in a folder in your BW-project you can use the ‘Retrieve Resource’ activity to get to the content.
You just have to set the resourcePath with the relative Path in your project and it will output the base64 data.











For training on TIBCO BusinessWorks mail us at [email protected]

Rule base to check for memory usage for a particular Queue.
Please follow the screen shots
1.  Select the JMS controller microagent and mention the required Queue name to be monitored.

2.    Select the condition for 80% threshold limit. Pending message size >= 83886080 (80% of total memory)

3.   Then provide the Alert message details and mail alert details.
      DL for prod is : [email protected]
      Prod Box is :  Your Unix Box Name
      Queue name is : EngineeringAndTechnology.virtualnuggets.com
      Note : This rule is already applied to Dev/QA box : Machine Name
      Rulename : QueueSize

Here i mentioned few common Trouble Shooting techniques in Tibco Iprocess

1) How to change the default table size in staffware database
Problem Description: To increase the table size to large (total space of 65GB)
Issue Resolution:
There are three tablesize files provided by the installer:   tablesizes, tablesizes.large, tablesizes.med
During installation, the default table sizes are taken from ?tablesizes? file. To increase the table size to large (total tablespace of 65GB), run the below command from your installation directory before running ?swinstall?. ?cp tablesizes.large tablesizes?

2) Problem while starting and stopping iProcess Engine
Problem Description:Timed out for response for stopping the server.? used to occur when stopping the server using ?swpro? user
Issue Resolution: Start and stop the server in the following sequence only:
swstart -p
swstart
swstop
swstop -p
This may happen when one of the iProcess clients is opened. To forcibly stop the server use the following commands
swstop -f
swstop
If the problem still persists, kill the processes started by ?swpro? user (ps -ef|grep $SWDIR)

3)Problem with User Validation in iProcess Client by enabling O/S User Validation
Problem Description: When user validation was enabled with O/S User Validation in staffpms file, the user was not allowed in even with correct ?swadmin? user name and password.
Issue Resolution: Temporary Fix: Removed the user validation flag in the configuration file on the server
Related Documentation: ? Section ?Specifying if Client Passwords are Required on Login? of TIBCO iProcess Engine Administrator?s Guide

4) Path to the jre file ?libjvm.so? while installing EAI Java Server Plug-in)
Problem Description:Installation of EAI Java Server Plug-in was successful, but got many errors like jre classpath not correct, etc during execution.
Issue Resolution: The path of ?jre? is to be specified as below during the installation of BW Connector on UNIX environment.
Path: $JRE/lib/sparc/server

5)Unable to initialise EAI Java Client plug-in in the iProcess Client
Problem Description: The EAI Java Plug-in is loaded but failed to initialize ? error message is displayed when using the EAI Java step in the iProcess Modeller.
Issue Resolution:
1)Set the SW_CLIENTCLASSPATH to $CLIENT\ eaijava\libs\bootstrap\bootstrap.jar and $CLIENT\java_common\libs\log4j-1.2.8.jar (where $CLIENT is set to the iProcess Client Directory)

6) Unable to load/initialize the EAI JAVA Server Plug-in
Problem Description: The EAI JAVA Server Plug-in is installed and registered but failed to load and the Login Daemon was suspended?
Error: ?The EAI Java Runtime Plug-in is not registered on all the servers ? The Login Daemon is not started
Issue Resolution:
1) Add the following in your .profile . The JAVA_HOME should be defined and exported before declaring the following.
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$JAVA_HOME/lib/sparc/native_threads:$JAVA_HOME/lib/sparc/server:$JAVA_HOME/lib/sparcexport LD_LIBRARY_PATH SW_SYSCLASSPATH=$SWDIR/eaijava/libs/bootstrap/log4j-1.2.8.jar:$SWDIR/eaijava/libs/bootstrap/bootstrap.jar export SW_SYSCLASSPATH SWJVM_OPTIONS=?-Xrs? export SWJVM_OPTIONS

7) Runtime Plugin error when using the EAI Java Step
Problem Description: When using a EAI Java step the following was the error encountered.
Error: ?The EAI Java Runtime Plug-in is not registered on all the servers?
Issue Resolution: 
1) Check whether the EAI Java plugin is registered on the iProcess Engine using the below command $SWDIR/util/sweaireg LIST [eai_type_name] [-m machine name] [-x]
2)Check for the s-bit permission for the following files (for unix operating systems)
$SWDIR/bin/swstart
$SWDIR/etc/procmgr
$SWDIR/etc/staffrpcbg
$SWDIR/etc/swbgmbd
If enabled remove the s-bit on these files. (After running the fixperms file all the above listed files will again have s-bit permission. So the s-bit permissions should be removed each time fixperms is executed)
Related Documentation:
?Installing the TIBCO Staffware EAI Java Plug-in?

8) The java class not found in EAI Java Plug-in
Problem Description: ?Error inside execute method of Java object-com.staffware.eaijava.FatalPluginException: Could not instantiate <> at com.staffware.eaijava.impl. SWGeneric Plugin.execute (SWGenericPlugin.java:240)?
Issue Resolution: Place the java class file in a jar file in the directory SWDIR/eaijava/libs/repository/user
Related Documentation: Post-installation Tasks and Manual installations in the ?Installing the TIBCO Staffware EAI Java Plug-in? Guide?

9) Unable to get the audit trail
Problem Description: Even if a case is started from Business Works and a case number is returned by it, the audit trail is not updated and no case exists with that case number?
Issue Resolution:
1) Check in the AUDIT_TRAIL table with the new case number.
2) If it still doesn?t exists, check whether an EAI step is used as the first step
3) If EAI step is the first step, Use a Transaction Control Step as commit point since the transaction is rolled back to the starting point when the EAI step (which is the first step) fails and no audit trail is recorded.

10) JMS messages sent by the EAI JAVA programs are merged
Problem Description: When the JMS Messages are polled by the EAI JAVA class file, the messages sent by it are either corrupted or merged and this occurred when a load of 1000 cases were started at once.
Issue Resolution: Remove the ?CACHE? option for the EAI JAVA Class in the ?EAI-CALL OUT DEFINITION? of the EAI JAVA Plugin.

11) Procedure in the iProcess Client is locked
Problem Description: Unable to edit the procedure in the iProcess Client since it?s locked by a staffware user.
Issue Resolution: 
1) Login to the staffware database with swpro (background database user) and run the following sql statements
(change the PROCNAME to the required Procedure name which is locked)
? delete procedure_lock where proc_id = (select proc_id from proc_index where proc_name = ?PROCNAME?)
? delete pm_objects_lock where object_guid = (select object_guid from pm_objects where object_name like ? PROCNAME?)

12) WorkItems get locked in the iProcess Client
Problem Description:The Work Items are locked in the iProcess Client due to various reasons like
? Improper closure of iProcess Client
? Network connection lost when the Work Item is opened, etc.,
Issue Resolution: Unlock the WorkItem with the following command
The user executing the command should be member /participant and should have MENUNAME of ADMIN.
swutil UNLOCKMAIL queuename reqid:hostname [/t]/t is for a test queue..
The reqid of the work item is found with the help of ?plist ?mv ? which gives a list of all the work items available for the queue and then search for the WorkItem with the help of fields like ?step name? and ?casenum?

13) Deadlines are not working on Saturdays and Sundays
Problem Description:The deadlines are not working as expected.
For example, if a step deadline of 5 min is sent to the work queue on Saturday, then the deadline date would be set for Monday and the step expires only on Monday and not within 5 minutes.
Issue Resolution: The 5th line in staffpms contains the information for the working days. Change them as required as shown in the following way in bold characters:
%2d/%2d/%4d\/\%s%s %s, %s\dmy\wdmy\%2d:%2d\:\ AM\ PM\Week\YYYYYYY

14) Adding mboxsets, queues, Oracle AQ queue, Oracle AQ queue table and their relationships for better handling of volumes
Description: For adding new Oracle AQ queues, mboxsets and assigning them to different processes for optimizing and enhancing the performance as desired.
Methodology:

1. Use SQLPLUS to connect to the Oracle instance.
$ORACLE_HOME/bin/sqlplus
connect swpro/staffpro1;

2. Create an AQ queue table called bgmboxtable3.
EXECUTE DBMS_AQADM.CREATE_QUEUE_TABLE (queue_table=> ?swpro.bgmboxtable3′,
queue_payload_> ?swpro.swlocalmsg?, comment=> ?3rd background mbox?,
compatible=> 8.1);

3. Create an AQ queue called bgmboxqueue3 in this queue table.
EXECUTE DBMS_AQADM.CREATE_QUEUE (queue_name=> ?swpro.bgmboxqueue3′, queue_table=>
?swpro.bgmboxtable3′, retry_delay=> 300, max_retries=> 12);

4. Start the bgmboxqueue3 queue.
EXECUTE DBMS_AQADM.START_QUEUE (queue_name => ?swpro.bgmboxqueue3′);

5. Grant the required privileges on the bgmboxqueue3 queue.
EXECUTE dbms_aqadm.grant_queue_privilege (privilege=> ?all?, queue_name=>
?bgmboxqueue3′, grantee=> ?swuser?, grant_option=> false );

6. Commit the changes, disconnect and exit.
commit;
disconnect;
exit;

7. Use the SWDIR\util\swadm utility to add a new message queue called BGMBOX3, which uses the bgmboxqueue3 queue.
cd $SWDIR/util swadm ADD_QUEUE BGMBOX3 Local 0001::bgmboxtable3:bgmboxqueue3

8. Add the BGMBOX3 queue to the BGMBSET Mbox set.
swadm ADD_QUEUE_TO_MBOXSET 1 8      
1 is the number of the BGMBSET Mboxset (from the swadm SHOW_MBOXSETS command) and 8 is the number of the message queue (from the swadm SHOW_QUEUES command).

The various commands used to list the various mboxsets, queues, relationships, process attributes
For listing:
? swadm show_mboxsets v
? swadm show_queues
? swadm show_all_attributes
? swadm show_processes
For adding:
? swadm ADD_MBOXSET
? swadm ADD_QUEUE_TO_MBOXSET

15) Adding CDQP to a queue
Description: To add CDQP so that it can be used for sorting, filtering and displaying based on the user defined Fields.
Procedure:
1) Write a file in the following format
 ;
 ;Add the fields TOWN and AGE as CDQPs.
 ;
F+TOWN,20,Town/City
Q+testqueue
C+TOWN

2) Run the command with either swadmin or with ?MENUNAME? as ADMIN and should be a participant/member of the queue.
$SWDIR/bin/ swutil QINFO $filePath
where $filePath is the path to the above saved file.

3) Export the CDQPs
SWDIR/bin/ swutil QINFO EXPORT [queuename [GLOBAL]]

4) Now the CDQP name is available for sorting, filtering and displaying either from iProcess Client or SPO.
in iProcess Client Click on the ?queue? and select the Queue>Change
Access Criteria and the new CDQP is displayed in the available fields in SPO filter criteria can set before fetching the cases or the workitems

16) Enabling DEBUG level while executing staffware util/etc/bin commands
Problem Description: How to turn on the debug level while executing staffware util/etc/bin commands
Issue Resolution: Run the util/etc/bin commands after setting the DEBUG environment variable as given below.
On Windows:
- In the registry (on the Staffware server) navigate to the following key:  HKEY_LOCAL_MACHINE\SOFTWARE\Staffware plc\Staffware Server\Nodes\
- Create a new string value in the key called ?DEBUG?
- Once created, double click it, and enter the following for the value data: T=255, f=15, F=-15, q=255, X=255, u=255, U=255, v=255, TIME=ABS

17) The Table and List area on User Administrator are locked
Problem Description: The Table and List area on the User Administrator are locked and unable to open or edit
Issue Resolution: Logout of the User Administrator and the check FLAG_TABLE of the staffware database.
Check the AREA_LOCKED columns. If it contains ?1? value set in any one of the columns then check for the MOVE_REQ flag. If it not ?1? then edit the table to change the AREA_LOCKED to ?0? and ?USER_NAME? field to empty.

NOTE:

 Its always better to do the changes in the database only after shutting down the server.

 If the MOVE_REQ flag is set to ?1? then some changes have been made to in that area of the User Administration and a ?MoveSysInfo? has been made. So all the data from the corresponding TSYS_ tables should be deleted and then the MOVE_REQ flag should be made to ?0? .In this case, changes should be made with the consultation of TIBCO SUPPORT.


For training on TIBCO IProcess mail us at [email protected]