PLSQL block for Publication process

If there is any issue entering parameters for Concurrent program or if you want to automate your publishing process, go for following plsql block:

DECLARE

  P_API_VERSION NUMBER;

  P_PUBLICATION_ID NUMBER;

  P_USER_ID NUMBER;

  P_RESP_ID NUMBER;

  P_APPL_ID NUMBER;

  X_RUN_ID NUMBER;

  X_STATUS NUMBER;

BEGIN

  P_API_VERSION := 1.0;

  P_PUBLICATION_ID := 64689;

  P_USER_ID := 1001530;  --EBUSINESS

  P_RESP_ID := 22687;  --Oracle Configurator Administrator

  P_APPL_ID := 708; --Configurator

  CZ_MODELOPERATIONS_PUB.PUBLISH_MODEL(

    P_API_VERSION => P_API_VERSION,

    P_PUBLICATION_ID => P_PUBLICATION_ID,

    P_USER_ID => P_USER_ID,

    P_RESP_ID => P_RESP_ID,

    P_APPL_ID => P_APPL_ID,

    X_RUN_ID => X_RUN_ID,

    X_STATUS => X_STATUS

  );

  DBMS_OUTPUT.PUT_LINE('X_RUN_ID = ' || X_RUN_ID);

  DBMS_OUTPUT.PUT_LINE('X_STATUS = ' || X_STATUS);

END;

Ensure you enable dbms output to check the return status.

Successful submission would return 0 as x_status.

You can also check in Configurator Developer  >  Publication tab for this publication, it should show as Complete.

P.S. All Configurator process APIs are listed in Implementation Guide of Configurator.
Change user_id, resp_id, appl_id as per your requirement.
For errors, refer cz_db_logs table.

Query to extract Oracle Configurator CX rule information

We can use following query to find out all the CX rules in the Configurator model. The query will display the information for the rules like rule_name, java class associated with it, event name, event scope, and oncommand event name.

SELECT DISTINCT RU.RULE_ID, 
  RU.NAME, 
  (SELECT NAME FROM CZ_SIGNATURES WHERE SIGNATURE_ID=EN.ARGUMENT_SIGNATURE_ID) AS EVENTNAME, 
  CLASS_NAME, 
  DECODE(EN.EVENT_EXECUTION_SCOPE, 1, 'Global', 2, 'Base Node SubTree', 4, 'Base Node', 'Unknown') AS SCOPE, 
  EN.DATA_VALUE oncommandEventName
FROM CZ_RULES RU, 
  CZ_EXPRESSION_NODES EN
WHERE DEVL_PROJECT_ID IN (131343) --for given devl_project_id
  AND RU.RULE_ID=EN.RULE_ID
  AND RU.RULE_TYPE=300 --for CX rules
  AND EN.ARGUMENT_SIGNATURE_ID IS NOT NULL --with valid event
  AND RU.DELETED_FLAG=0 --ignore deleted nodes
  AND EN.DELETED_FLAG=0
  AND EN.EXPR_PARENT_ID IS NULL --definition is only on parent node of expression tree
;

This query is useful at times to find out all CX rules with base node subtree event scope which may usually cause performance issue if its unwanted. You can always add other parameters/clauses to filter information as per your need.