Some more interesting chess problems collection for the week ending 30/5.
Position: White to Move and Checkmate in shortest possible moves.
1)
2)
3)
4)
Some more interesting chess problems collection for the week ending 30/5.
Position: White to Move and Checkmate in shortest possible moves.
1)
Some more chess problems for this week. Hope they would give a good challenge for somebody who are constantly on the look for challenging chess puzzles.
Position: White to move and checkmate in shortest possible moves.
1)
As per the latest update, Tamilnadu +2 HSC results can be expected tomorrow. More details are available below
Link
In this section, let us discuss the preliminary setup that needs to be done in PeopleSoft to support qtip. For the examples, that I will be describing here, I have used the version 1.0.0-rc3 of the qTip. So get to the qTip download page and download jQuery and "Production" version of the tooltip plugin.
When you extract the contents, you will be able to find the following files :
1) jquery-1.3.2.min.js
2) jquery.qtip-1.0.0-rc3.min.js
We will be in need of these files to support the flashy tooltips displayed in PeopleSoft. To enable them, you have to copy these scripts to the "script" directory of the webserver domain in PeopleSoft.
The script directory is normally located in this path:
webserv/<DomainName>/applications/peoplesoft/PORTAL/<DomainName>/script
<html> <head> <script type="text/javascript" src="/<domainname>/script/jquery.1.3.2.min.js"></script> <script type="text/javascript" src="/<domainname>/script/jquery.qtip-1.0.0.min.js"></script> This has to be mentioned in this order. Also ensure that the file names mentioned here (.js ones) are exactly the same as you have uploaded in the web server script folder. <script type="text/javascript"> All tips are loaded after the document is completely loaded in the browser. $(document).ready(function(){ $("#TEST_REC_FIELD1").attr("title","I triggered a ToolTip"); $("#img11").attr("title","Tooltip on Images"); $("#RE_LEVEL0_TMP_CAPTURE_ID\\$0").attr("title","A Tooltip for the Grid Record"); we are using the "attr" method to set "title" attributes for our text field (TEST_REC_FIELD1 is the id of the field. Replace this with the ID of your text field), image ("img11" is the id of the image. Replace this with the ID of your image),and scroll level 1 field (RE_LEVEL0_TMP_CAPTURE_ID\\$0 is the id of the 1st element of the grid. Replace this with the ID of your grid element. Note that we are using two '\\' slashes to escape the "$" sign). $("#TEST_REC_FIELD1").qtip({ style: { name: 'blue' }, position: { corner: { target: 'rightBottom', tooltip: 'bottomLeft' } } }); We define the style and positioning of the text field here. $("#RE_LEVEL0_TMP_CAPTURE_ID\\$0").qtip({ style: { name: 'red' }, position: { corner: { target: 'rightBottom', tooltip: 'bottomLeft' } } }); We define the style and positioning of the grid element here. $("#img11").qtip({ style: { name: 'cream' // Inherit from preset style }, position: { corner: { target: 'rightBottom', tooltip: 'bottomLeft' } } }); We define the style and positioning of the image here. Note that the image is another HTML area, containing a constant code <img id='img11' src=%Image(HELPIMAGEPSFT) > }); </script> </head> <body> </body> </html> </body> </html> |
<script type="text/javascript" src="/<domainname>/script/jquery.1.3.2.min.js"></script> <script type="text/javascript" src="/<domainname>/script/jquery.qtip-1.0.0.min.js"></script> <script type="text/javascript"> $(document).ready(function(){ $("#TEST_REC_FIELD1").qtip({ => TEST_REC_FIELD1, field for which we intend to show a tooltip style: { name: 'blue' }, content: "%bind(:1)", => Note that we are binding the contents dynamically here. This will be passed from the code. position: { corner: { target: 'rightBottom', tooltip: 'bottomLeft' } } }); }); </script> |
If %UserId = "VP1" Then TEST_REC.HTMLAREA.Value = GetHTMLText(HTML.QTIP_HTML, "You have full Rights on this page") => We pass the input dynamically here. Else TEST_REC.HTMLAREA.Value = GetHTMLText(HTML.QTIP_HTML, "Hi there, welcome") => and here. End-If; |
http://dge1.tn.nic.in/ | Official website to know the results. At the time of writing, the results are not announced yet. |
http://dge2.tn.nic.in/ | I believe this is another mirror to the result website. It has a banner stating "Await for Announcement" |
http://www.kalvimalar.com/examresults.asp | Through this site you can register to get the information about your results directly via SMS or by email. Very useful, just in case you are not able to get the results from any website due to bandwidth issues. |
http://tnresults.nic.in/ | Tamilnadu state directorate of Government examinations, direct link. Candidates need to provide their registration number to get the results from this site. |
TamilNadu +2 results for 2010 will be declared by 12th May 2010..Some links to check the examination results online are given below
Results
I've got some questions wherein, users who tried to replicate the SOAP implementation in PeopleSoft, ended up with an integration gateway error. The error details are given below:-
Mime-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_29_25154556.1272944790597"
Content-ID: PeopleSoft-Integration-Broker-Internal-Mime-Message
------=_Part_29_25154556.1272944790597
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Content-ID: IBInfo
<?xml version="1.0"?><IBInfo><Status><StatusCode>20</StatusCode><MsgSet>158</MsgSet><MsgID>10409</MsgID><DefaultTitle>Integration Gateway Error</DefaultTitle></Status></IBInfo>
------=_Part_29_25154556.1272944790597--
Gateway Unmarshalling: The MimeContent of the message is not a MimeMultipart message as expected.
The exact log in the Integration gateway is as given below
com.peoplesoft.pt.integrationgateway.common.MessageUnmarshallingException: IBMessage:setContent(). Message content is not a MimeMesage
at com.peoplesoft.pt.integrationgateway.framework.IBMessage.setContent(IBMessage.java:96)
at com.peoplesoft.pt.integrationgateway.framework.IBMessage.setContent(IBMessage.java:152)
at com.peoplesoft.pt.integrationgateway.framework.IBRequest.<init>(IBRequest.java:76)
at com.peoplesoft.pt.integrationgateway.framework.InternalIBRequest.<init>(InternalIBRequest.java:247)
at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.manageRequest(GatewayManager.java:262)
at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.connect(GatewayManager.java:211)
at com.peoplesoft.pt.integrationgateway.listeningconnector.PeopleSoftListeningConnector.doPost(PeopleSoftListeningConnector.java:123)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:996)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6455)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3664)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
The link to the original post is available here. This problem is due to incorrect configuration of the node definition in PeopleSoft. Make sure that the node definitions are properly setup as given in the original post.
That should rectify this issue.
This would be the last part of the cache analysis exercise in PeopleSoft. If you are landing here directly, make sure you check out the previous parts;
Until now, we have a got a good idea of how things behave when they are not cached. We had a look at the SQLs executed by the Application Server, and also went to an extent of understanding what might have happened behind these SQLs; all setup on a simple page definition in PeopleSoft.To conclude this series, let us try to understand the whole scenario when the definitions are cached.
Not so surprisingly, the number of SQLs executed in this case is far less. A brief summary is provided below. It starts with queries against PSVERSION
SELECT VERSION FROM PSVERSION WHERE OBJECTTYPENAME = 'SYS'
SELECT OBJECTTYPENAME, VERSION FROM PSVERSION
What I interpret here is that, PeopleSoft tries to get the version information to see if something has "changed". If not, it just loads the definitions from the cache. This is also evident against each "save" event of the object definition in Application Designer, wherein the version count is incremented by 1.
After this, the only queries (specific to my scenario) that gets executed are, the queries against user personalization.
SELECT OBJNAME, FLAG, PTCUSTOMFORMAT FROM PSUSEROBJTYPE WHERE MENUNAME = :1 AND PNLGRPNAME = :2 AND PNLNAME = :3 AND OPRID = :4 AND FIELDTYPE = :5
SELECT PTCUSTOMFORMAT FROM PSUSEROBJTYPE WHERE MENUNAME = :1 AND PNLGRPNAME = :2 AND PNLNAME = :3 AND OPRID = :4 AND FIELDTYPE = :5
SELECT PTCUSTOMFORMAT FROM PSUSEROBJTYPE WHERE MENUNAME = :1 AND PNLGRPNAME = :2 AND PNLNAME = :3 AND OPRID = :4 AND FIELDTYPE = :5
The page gets loaded after this, all in a flash..In a sense, this gives a huge performance benefit to the users using the system, and also minimizes the overhead of reloading unchanged definitions from the database.