-
Notifications
You must be signed in to change notification settings - Fork 8
/
SapHrOperationProvisioning.xml
103 lines (97 loc) · 3.76 KB
/
SapHrOperationProvisioning.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE sailpoint PUBLIC "sailpoint.dtd" "sailpoint.dtd">
<sailpoint>
<Rule language="beanshell" name="Provisioning Rule Template per operations rule for SAP HR" type="SapHrOperationProvisioning">
<Description>This rule is used by the SAP HR connector for
provisioning
of the data .</Description>
<Signature returnType="ProvisioningResult">
<Inputs>
<Argument name="context">
<Description>
A sailpoint.api.SailPointContext object that can be used to query
the database if necessary.
</Description>
</Argument>
<Argument name="log">
<Description>
The log object associated with the SailPointContext.
</Description>
</Argument>
<Argument name="application">
<Description>The application whose data file is being
processed.</Description>
</Argument>
<Argument name="schema">
<Description>The Schema currently in use.</Description>
</Argument>
<Argument name="destination">
<Description>A connected/ready to use
com.sap.conn.jco.JCoDestination object that can be used to
call
bapi, function modules and call to SAP tables. This is the main
object used in making BAPI calls using the JCo interface.This
destination object is shared with the connector
implementation and
the connector controls the destination's lifecycle.</Description>
</Argument>
<Argument name="plan">
<Description>The ProvisioningPlan created against the SAP
application.</Description>
</Argument>
<Argument name="request">
<Description>The ProvisioningRequest created against the SAP
application.</Description>
</Argument>
<Argument name="connector">
<Description>The SAP connector that is being used to
communicate
with SAP. This class is here for convenience as there are many
utility methods that make calling Function Modules and
doing table
lookup easier.</Description>
</Argument>
</Inputs>
<Returns>
<Argument name="result">
<Description>A Provisioning Result object is desirable to
return the
status.IT can be a new object or part of Provisioning Plan</Description>
</Argument>
</Returns>
</Signature>
<ReferencedRules>
<Reference class="sailpoint.object.Rule" name="Global Rule Library"/>
</ReferencedRules>
<Source>
<![CDATA[
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import sailpoint.api.SailPointContext;
import org.apache.commons.logging.Log;
import sailpoint.object.TaskResult;
import sailpoint.object.Application;
import sailpoint.object.Schema;
import com.sap.conn.jco.JCoDestination;
import sailpoint.object.ProvisioningPlan;
import sailpoint.object.ProvisioningRequest;
import sailpoint.connector.SAPHRConnector;
//Log mylogger = LogFactory.getLog("rule.SapHrOperationProvisioning");
//mylogger.debug("Start SapHrOperationProvisioning");
//add the following lines to IIQ Log4j properties file to use this logger
//logger.SapHrOperationProvisioning.name=rule.SapHrOperationProvisioning
//logger.SapHrOperationProvisioning.level=debug
//Available Input Variables
//application;
//schema;
//destination;
//plan;
//request;
//connector;
//mylogger.debug("End SapHrOperationProvisioning");
//return ProvisioningResult
return null;
]]>
</Source>
</Rule>
</sailpoint>