How to set Parental Control on your Android Tablets and Smartphones.

The following are some useful database queries you can run against the LiveCycle ES2 database to understand/debug LiveCycle Process Management. These apply to MySQL. Other DBMSs might require slight changes. ‘adobe’ is the schema name.

DISPLAY ALL LONG-LIVED ORCHESTRATIONS (PROCESSES) SELECT id as PROCESS_ID, service_name as ORCHESTRATION_NAME, start_time as START_TIME, TIMEDIFF(complete_time, start_time) AS ELAPSED_TIME FROM `adobe`.`tb_process_instance` ORDER BY create_time

Oracle Example ——————– SELECT id as PROCESS_ID, service_name as ORCHESTRATION_NAME, to_char(adobe.tb_process_instance.start_time, ‘DD-Mon-YYYY HH24:MI:SS’) as START_TIME, trunc(86400*(complete_time – start_time)) AS ELAPSED_SECONDS FROM adobe.tb_process_instance ORDER BY create_time

Oracle Example – Display New Processes —————————————————- SELECT id as PROCESS_ID, service_name as ORCHESTRATION_NAME, to_char(adobe.tb_process_instance.start_time, ‘DD-Mon-YYYY HH24:MI:SS’) as START_TIME, to_char(adobe.tb_process_instance.complete_time, ‘DD-Mon-YYYY HH24:MI:SS’) as COMPLETE_TIME, trunc(86400*(complete_time – start_time)) AS ELAPSED_SECONDS FROM adobe.tb_process_instance WHERE id > 2000 ORDER BY id

DISPLAY DETAILS OF ALL PROCESSES AND THEIR INDIVIDUAL ACTIONS SELECT adobe.tb_process_instance.id AS PROCESS_ID, adobe.tb_process_instance.start_time AS PROCESS_START_TIME, adobe.tb_process_instance.complete_time AS PROCESS_COMPLETE_TIME, adobe.tb_action_instance.id AS ACTION_ID, adobe.tb_action_instance.start_time AS ACTION_START_TIME, adobe.tb_action_instance.complete_time AS ACTION_COMPLETE_TIME FROM adobe.tb_process_instance, adobe.tb_action_instance WHERE adobe.tb_process_instance.id = adobe.tb_action_instance.process_instance_id ORDER BY adobe.tb_process_instance.id, adobe.tb_action_instance.id

Oracle Example ———————- SELECT adobe.tb_process_instance.id AS PROCESS_ID, to_char(adobe.tb_process_instance.start_time, ‘DD-Mon-YYYY HH24:MI:SS’) AS PROCESS_START_TIME, to_char(adobe.tb_process_instance.complete_time, ‘DD-Mon-YYYY HH24:MI:SS’) AS PROCESS_COMPLETE_TIME, adobe.tb_action_instance.id AS ACTION_ID, to_char(adobe.tb_action_instance.start_time, ‘DD-Mon-YYYY HH24:MI:SS’) AS ACTION_START_TIME, to_char(adobe.tb_action_instance.complete_time, ‘DD-Mon-YYYY HH24:MI:SS’) AS ACTION_COMPLETE_TIME FROM adobe.tb_process_instance, adobe.tb_action_instance WHERE adobe.tb_process_instance.id = adobe.tb_action_instance.process_instance_id ORDER BY adobe.tb_process_instance.id, adobe.tb_action_instance.id

DISPLAY COMPLETE DETAILS OF A PARTICULAR PROCESS SELECT * FROM adobe.tb_process_instance, adobe.tb_action_instance, adobe.tb_job_instance WHERE adobe.tb_process_instance.id = adobe.tb_action_instance.process_instance_id AND adobe.tb_process_instance.long_lived_invocation_id = adobe.tb_job_instance.public_id AND adobe.tb_process_instance.id = 101 ORDER BY adobe.tb_process_instance.id, adobe.tb_action_instance.id

DISPLAY TIME TAKEN BY ACTIONS IN A PROCESS SELECT id as ACTION_ID, TIMEDIFF(complete_time, start_time) AS ELAPSED_TIME FROM adobe.tb_action_instance WHERE process_instance_id = 301