Abstract: A set of attributes are identified within a received input request of a workflow process. The attributes at least in part represent historical process performance of similar workflow processes. Each of the attributes are weighted into a weighted process prioritization data set based upon the historical workflow process performance. The input request is assigned to a process priority based upon the weighted process prioritization data set.

Abstract: Input data of an input request is received. The input data includes a set of attributes. For each attribute of the set of attributes, a weight is assigned to the attribute based, at least in part, upon historical data relating to workflow performance, to form a respective corresponding weighted attribute. A process priority value is assigned to the input data of the input request based, at least in part, upon on the weighted attributes.

Abstract: Input data of an input request is received. The input data includes a set of attributes. For each attribute of the set of attributes, a weight is assigned to the attribute based, at least in part, upon historical data relating to workflow performance, to form a respective corresponding weighted attribute. A process priority value is assigned to the input data of the input request based, at least in part, upon on the weighted attributes.

Abstract: A set of attributes are identified within a received input request of a workflow process. The attributes at least in part represent historical process performance of similar workflow processes. Each of the attributes are weighted into a weighted process prioritization data set based upon the historical workflow process performance. The input request is assigned to a process priority based upon the weighted process prioritization data set.

Abstract: In response to receipt of a process-level input request that is subject to business-level requirements, multiple sets of attributes are identified. The sets of attributes are each from one of multiple informational domains that represent processing factors associated with at least the process-level input request, contemporaneous infrastructure processing capabilities, and historical process performance of similar processes. The multiple sets of attributes from the multiple informational domains are hashed as a vector into an initial process prioritization. The attributes of the hashed vector of the multiple sets of attributes from the multiple informational domains are weighted in the initial process prioritization into a hashed-weighted resulting process prioritization. The process-level input request is assigned to a process category based upon the hashed-weighted resulting process prioritization.

Abstract: In response to receipt of a process-level input request that is subject to business-level requirements, multiple sets of attributes are identified. The sets of attributes are each from one of multiple informational domains that represent processing factors associated with at least the process-level input request, contemporaneous infrastructure processing capabilities, and historical process performance of similar processes. The multiple sets of attributes from the multiple informational domains are hashed as a vector into an initial process prioritization. The attributes of the hashed vector of the multiple sets of attributes from the multiple informational domains are weighted in the initial process prioritization into a hashed-weighted resulting process prioritization. The process-level input request is assigned to a process category based upon the hashed-weighted resulting process prioritization.

Abstract: In response to receipt of a process-level input request that is subject to business-level requirements, multiple sets of attributes are identified. The sets of attributes are each from one of multiple informational domains that represent processing factors associated with at least the process-level input request, contemporaneous infrastructure processing capabilities, and historical process performance of similar processes. The multiple sets of attributes from the multiple informational domains are hashed as a vector into an initial process prioritization. The attributes of the hashed vector of the multiple sets of attributes from the multiple informational domains are weighted in the initial process prioritization into a hashed-weighted resulting process prioritization. The process-level input request is assigned to a process category based upon the hashed-weighted resulting process prioritization.

Abstract: In response to receipt of a process-level input request that is subject to business-level requirements, multiple sets of attributes are identified. The sets of attributes are each from one of multiple informational domains that represent processing factors associated with at least the process-level input request, contemporaneous infrastructure processing capabilities, and historical process performance of similar processes. The multiple sets of attributes from the multiple informational domains are hashed as a vector into an initial process prioritization. The attributes of the hashed vector of the multiple sets of attributes from the multiple informational domains are weighted in the initial process prioritization into a hashed-weighted resulting process prioritization. The process-level input request is assigned to a process category based upon the hashed-weighted resulting process prioritization.

Abstract: In response to receipt of a process-level input request that is subject to business-level requirements, multiple sets of attributes are identified. The sets of attributes are each from one of multiple informational domains that represent processing factors associated with at least the process-level input request, contemporaneous infrastructure processing capabilities, and historical process performance of similar processes. The multiple sets of attributes from the multiple informational domains are hashed as a vector into an initial process prioritization. The attributes of the hashed vector of the multiple sets of attributes from the multiple informational domains are weighted in the initial process prioritization into a hashed-weighted resulting process prioritization. The process-level input request is assigned to a process category based upon the hashed-weighted resulting process prioritization.

Abstract: In response to receipt of a process-level input request that is subject to business-level requirements, multiple sets of attributes are identified. The sets of attributes are each from one of multiple informational domains that represent processing factors associated with at least the process-level input request, contemporaneous infrastructure processing capabilities, and historical process performance of similar processes. The multiple sets of attributes from the multiple informational domains are hashed as a vector into an initial process prioritization. The attributes of the hashed vector of the multiple sets of attributes from the multiple informational domains are weighted in the initial process prioritization into a hashed-weighted resulting process prioritization. The process-level input request is assigned to a process category based upon the hashed-weighted resulting process prioritization.

Abstract: A method includes encoding a session identifier into a uniform resource identifier (URI) associated with a TCAP Begin message request originating at an application server, where the session identifier identifies a communication session. The method also includes transmitting the TCAP Begin message request from the application server to a transaction capabilities application part (TCAP) interface and receiving a TCAP Continue message request from the TCAP interface with the TCAP Continue message request including the encoded URI. The method includes correlating the TCAP Continue message request to the communication session that originated the Begin request identified by the session identifier in the received URI and routing the TCAP Continue message request to the communication session.

Abstract: An apparatus, system, and method are disclosed for validating application server replication errors. The method includes receiving a first information message with a test sequence from a caller. The caller is engaged in a communication session with a callee according to a communication protocol and the communication session is managed by a first application server. The method also includes storing the test sequence in a replicable data structure on the first application server. The replicable data structure is replicated to a second application server to form a replicated data structure and both servers operate within an active-active configuration. The method also includes receiving a second information message from the caller. The second information message includes a confirmation sequence. In addition, the method includes determining a replication error in response to comparing the stored test sequence in the replicated data structure with the confirmation sequence.

Abstract: An apparatus, system, and method are disclosed for validating application server replication errors. The method includes receiving a first information message with a test sequence from a caller. The caller is engaged in a communication session with a callee according to a communication protocol and the communication session is managed by a first application server. The method also includes storing the test sequence in a replicable data structure on the first application server. The replicable data structure is replicated to a second application server to form a replicated data structure and both servers operate within an active-active configuration. The method also includes receiving a second information message from the caller. The second information message includes a confirmation sequence. In addition, the method includes determining a replication error in response to comparing the stored test sequence in the replicated data structure with the confirmation sequence.

Abstract: A method includes encoding a session identifier into a uniform resource identifier (URI) associated with a TCAP Begin message request originating at an application server, where the session identifier identifies a communication session. The method also includes transmitting the TCAP Begin message request from the application server to a transaction capabilities application part (TCAP) interface and receiving a TCAP Continue message request from the TCAP interface with the TCAP Continue message request including the encoded URI. The method includes correlating the TCAP Continue message request to the communication session that originated the Begin request identified by the session identifier in the received URI and routing the TCAP Continue message request to the communication session.