Siebel

BI Publisher

getSecurityModel

XMLP Reports Server Requests BIPs Security Model by making the getSecurityModel webservice call to BI Publisher

POST /xmlpserver/services/PublicReportService_v11 HTTP/1.1 getSecurityModel

HTTP/1.1 200 OK <getSecurityModelReturn>SIEBEL</getSecurityModelReturn> XMLP Reports Server Component requests the available report parameters by making the getTemplateParameters webservice call to BI Publisher. In the call the absolute path to the report is supplied in the <reporAbsolutePath> tag. The UserID and password of the Siebel user and password are supplied in the <userID> and <password> tags.

BIP responds with SIEBEL indicating that Siebel Security Model is used

POST /xmlpserver/services/PublicReportService_v11 HTTP/1.1 getTemplateParameters <getTemplateParameters xmlns="http://../v11/PublicReportService"> <reportAbsolutePath>/SiebelCRMReports/.xdo</reportAbsolutePath> <userID>CURSIST_AMBER01</userID> <password>Welkom2009</password> </getTemplateParameters>

POST /eai_nld/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=BIPW SUSR&Password=LOwv0uBaV58S HTTP/1.0 BIP-Siebel/Security:Authenticate <Authenticate_Input xmlns="http://siebel.com/BIP-Siebel/Security"> <username>SIEBELUSER01</username> <password>DoNotTell</password> </Authenticate_Input> HTTP/1.1 200 OK <ns:Authenticate_Output xmlns:ns="http://siebel.com/BIP-Siebel/Security"> <ns:ok>true</ns:ok> </ns:Authenticate_Output>

BI Publisher makes a BIPSiebel/Security:Authenticate webservice call to Siebel to authenticate the Siebel user using the credentials supplied in the runReport inbound webservice call.

getTemplateParameters

EAI ObjectManager validates the received username and password using the configured security adapter. If credentials are validated successfully, it responds with the value true in the namespace ok.

ObjectManager

EAIObjMgr

EAI ObjectManager retrieves the responsibilities assigned to the employee from the Siebel user data. The employee is stored in UPPER-case , and queries are case-sensitive. Therefore supplied username must be in UPPER-case.

POST /eai_nld/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=BIPW SUSR&Password=LOwv0uBaV58S HTTP/1.0 BIP-Siebel/Security:GetRoles" <GetRoles_Input xmlns="http://siebel.com/BIP-Siebel/Security"> <username>SIEBELUSER01</username> </GetRoles_Input> HTTP/1.1 200 OK <ns:GetRoles_Output xmlns:ns="http://siebel.com/BIP-Siebel/Security"> <ns:csvRoles>...,XMLP_DEVELOPER,CVOM</ns:csvRoles> </ns:GetRoles_Output>

BI Publisher makes a BIPSiebel/Security:GetRoles webservice call to Siebel to retrieve the list of responsibilites assigned to the Siebel employee.

HTTP/1.1 200 OK <getTemplateParametersResponse xmlns="http://xmlns....PublicReportService"> <getTemplateParametersReturn xsi:nil="true"/> </getTemplateParametersResponse>

BI Publisher returns the template parameters in the getTemplateParameters webservice response. In this example, the template contains no parameters.

XMLP Reports Server Component requests to run a report by making the runReport webservice call to BI Publisher. In the call the Format, Locale and abolute path to the report on BIP are supplied in the <reportRequest> tag. The UserID and password of the Siebel user and password are supplied in the <userID> and <password> tags.

POST /xmlpserver/services/PublicReportService_v11 HTTP/1.1 runReport <runReport> <reportRequest> <attributeFormat> ... </reportRequest> <userID>SIEBELUSER01</userID> <password>DoNotTell</password> </runReport? BI Publisher makes a BIPSiebel/Security:Authenticate webservice call to Siebel to authenticate the Siebel user using the credentials supplied in the runReport inbound webservice call.

POST /eai_nld/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=BIPW SUSR&Password=LOwv0uBaV58S HTTP/1.0 BIP-Siebel/Security:Authenticate <Authenticate_Input xmlns="http://siebel.com/BIP-Siebel/Security"> <username>SIEBELUSER01</username> <password>DoNotTell</password> </Authenticate_Input> EAI ObjectManager validates the received username and password using the configured security adapter. If credentials are validated successfully, it responds with the value true in the namespace ok. HTTP/1.1 200 OK <ns:Authenticate_Output xmlns:ns="http://siebel.com/BIP-Siebel/Security"> <ns:ok>true</ns:ok> </ns:Authenticate_Output>

runReport

EAI ObjectManager retrieves the responsibilities assigned to the employee from the Siebel user data. The employee is stored in UPPER-case , and queries are case-sensitive. Therefore supplied username must be in UPPER-case.

POST /eai_nld/ start.swe?SWEExtSource=SecureWebService&SWEExtCmd=Execute&UserName=BIPW SUSR&Password=LOwv0uBaV58S HTTP/1.0 BIP-Siebel/Security:GetRoles" <GetRoles_Input xmlns="http://siebel.com/BIP-Siebel/Security"> <username>SIEBELUSER01</username> </GetRoles_Input>
HTTP/1.1 200 OK <ns:GetRoles_Output xmlns:ns="http://siebel.com/BIP-Siebel/Security"> <ns:csvRoles>...,XMLP_DEVELOPER,CVOM</ns:csvRoles> </ns:GetRoles_Output>

BI Publisher makes a BIPSiebel/Security:GetRoles webservice call to Siebel to retrieve the list of responsibilites assigned to the Siebel employee.

HTTP/1.1 200 OK <runReportResponse xmlns="http://xmlns.oracle.com/oxp/service/v11/PublicReportService"> <runReportReturn> <reportBytes>JVBEUGFnZ.......cNCiUlRU9GDQo=</reportBytes> <reportContentType>application/pdf</reportContentType> <reportFileID xsi:nil="true"/><reportLocale xsi:nil="true"/> </runReportReturn> </runReportResponse> BI Publisher returns the report in the runReport webservice response.

www.petervannes.nl