![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• A transaction can be defined as a single instruction, such as a case start. (If the call to SW_CASESTART succeeds then a commit is immediately performed.)
Invalid sequence type (seq_type) (ID:001000) Unable to connect to server errno (Error) (ID:001003)Error is a description of the error returned by the SQL Server sp_OAMethod system stored procedure. Unable to verify connection (Return) (ID:001004) Failed to execute sequences - Source (ID:001005)Source is a description of the source of the error. Failed to retrieve sequence number - Source (ID:001006)Source is a description of the source of the error. Procedure details not found in database for procedure name=proc_name (ID:001010) Procedure version not found in database for procedure name=proc_name major_version minor_version (ID:001013) Suspend type (suspend_type) is invalid, expected 2 (suspend) or 0 (activate) (ID:001014) Case (case_num) is already active (ID:001036) Case (case_num) is dead (ID:001037) Case (case_num) is already suspended (ID:001038) Sub-Proc casenum not found in database for Procedure proc_name, Case Number case_num, Step Name step_name, Sub-proc sub_proc_name (ID:001018) Failed to find case information for case: case_num (ID:001019) Case (case_num) is dead (ID:001039) SSOLite stored procedures access the sequences table to obtain work item and case number sequence numbers. This locks the table, preventing other iProcess processes from accessing it, for the duration of the transaction.This could cause a problem if, for example, you were batch starting a large number of cases as part of a single transaction.To prevent this, SSOLite stored procedures use SQL-DMO to connect back to the iProcess database as a separate transaction when obtaining sequence numbers.
1. use Windows Authentication to validate the connection to the iProcess database.
2. have the Server Administrators SQL Server Role assigned.SSOLite stored procedures write messages to the BG processes using the default background message queues, using a round-robin allocation on a per-session basis. This means that every time a new database session is started the first defined queue (BGMBOX1) is used first. As a result, BGMBOX1 can become overloaded if database sessions are not persisted.You can override this default behavior for specific transactions by using the SW_SET_QUEUE and SW_UNSET_QUEUE control procedures.
1. Create a new Mbox set named SSOLITE. (The Mbox set can use either existing message queues or new ones.)
2. Set the MBSET_WRITE_BG process attribute for your application to assign the SSOLITE1 queue to it. All messages posted to a BG process by the SSOLite stored procedures will now use the SSOLITE Mbox set.
Because the SSOLite stored procedures cache queue information, you must shut down and restart all database connections if you change your message queue configuration in this way.
• "Administering Message Queues and Mbox Sets" in TIBCO iProcess Engine Administrator's Guide.Use the SW_SET_PRIORITY control procedure to set the internal message queue priorities and the SW_UNSET_PRIORITY control procedure to restore the default message queue priorities.If the internal message queue priorities are not set, the messages will be processed in the order of SW_CP_VALUE or SW_IP_VALUE when using iProcess Workspace (Windows) to process work items.
• If the value of the SW_CP_VALUE field is set, the message will be processed in the order of SW_CP_VALUE regardless of the message queue priority that is set by using the SW_SET_PRIORITY control procedure.
• If the SW_CP_VALUE field is not set, the message will be processed in the order of the message queue priority that is set using the SW_SET_PRIORITY control procedure.
• If both the SW_CP_VALUE field and the SW_SET_PRIORITY control procedure are not set for the message priority, the message priority will be set to the default value of the SW_CP_VALUE field, 50.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |