Mark Enjam

 Complex joins are joins which have following diffrences from a PK-FK joins # Complex joins can have conditional mappings like >,<,>=,NOT,AND,etc apart from '=' whereas the PK-FK joins are always '='. # PK-FK joins are always (1-N), whereas complex joins can have (1 - 0,1) and (0,1 - N) kind of relationships PK-FK is always 1-N and  complex joins can have (1-0,1) and (0,1-N). PK-FK is always 1-N and  complex joins can have (1-0,1) and (0,1-N). as per my knowledge i understand that 1-N is one -- many relation . complex join:- complex join are used in physical layer in between two tables where ever that do not involved primary key and forgin key relationship. Foregin Key:- by using the forgin key we can define the joins between two tables. joins between is 1:M or M:M. if we want to define many:many relationship we have to use bridge tables. how to configure the complex join? Ans:  complex join is that join within join where as two tables doesn't have any fore

Question 1 : What are REST APIs?  Answer: REST stands for Representational state transfer. It is a protocol for data transfer using HTTP methods. Usually REST API uses JSON format to communicate as it is simpler and lightweight than XML uestion 2: Whats the architecture changes required in Siebel to implement REST API?  Answer:  Oracle has introduced java web containers and Proxy Object Manager to manage them at run time. Architecture looks like below: Question 3: What is the use of Siebel REST Proxy Object Manager? Answer: Siebel REST Proxy Object Manager is a new component which was introduced in Siebel IP17 to manage Java Web Containers on the Siebel Server. Requests from the web server is served by java web container by sending the request to EAI Object Manager. Siebel REST Proxy Object Manager is responsible for turning the Java Web Container On or Off. Question 4:  What are the URL Patterns for data and business services? Answer: Business services can be directly invoked as RESTf

 There are number of files that we come across in Siebel and we don't have idea about their usage and role in our application. Here in this post we will discuss about all the important files. Siebel_sia.srf eapps.cfg eapps_sia.cfg gateway.cfg diccache.dat Enterprise_server.shm file application.cfg lbconfig.txt Siebns.dat Siebel_sia.srf Siebel SRF file also known as Siebel Repository File (SRF) is a compressed, read only file that contains compiled version of Siebel repository. So all the object definitions and scripts that are defined in Siebel Tools are compiled into one single file which is will be used by Siebel Application at run time. This SRF file is normally at "\root\siebsrvr\objects\enu” with the file extension srf. It is very important that the active Siebel Repository should always be in sync with the SRF. Please do not get confuse between Siebel repository and Srf file. The main difference between Repository and SRF is that Repository is the collection of all Siebe

when we are trying to close the service Request unless and until all the activities under that service request has status “Done”*/ Ans: Multiple ways we can do  1. Through Script 2. Through DVM 3. Through WF 1. function BusComp_PreSetFieldValue (FieldName, FieldValue) {    if(FieldName == "Status")    {       if(FieldValue == "Closed")         {           var bosrvreq = TheApplication().ActiveBusObject();           var bcsrvreq = bosrvreq.GetBusComp("Service Request");           var bcaction = bosrvreq.GetBusComp("Action");           var srid = this.GetFieldValue("Id");                     with(bcaction)           {             ActivateField("Status");             ActivateField("Activity SR Id");             SetViewMode(3);             ClearToQuery();             SetSearchSpec("Activity SR Id", srid);             ExecuteQuery();                        }                       var firstrec = bcaction.FirstRec

 

 

  When I started configuring Siebel, I was mostly self-taught, which means that I usually settled for the first way I found of accomplishing my goal. Setting the primary record on a multi-value group through script is one example. My method: query for the record I needed in the child buscomp, obtain the row id, and then use that row id to update the primary id field of the parent. For example, if I needed to set the primary position on the Account buscomp, I would begin by looking up the position id, then I would use a SetFieldValue statement to set the Primary Position Id with the id I had retrieved. Wrong approach!  That is the dangerous way. A scripting error will potentially corrupt your database in the same way direct sql could, by breaking its referential integrity. Directly setting a primary id field is not supported by Oracle. The feature I didn't understand, which makes the process much easier and safer, is a system field called SSA Primary. You may have noticed this field