neptunlabs

Department Hierarchy Query. Partners to identify nodes on the tree with no manager. Information into a PeopleSoft page that would.

Football Manager 2009 Full Game Pc. 'Hi, I'm relatively new to this, so hope this isn't a dumb question. We have a number of peoplesoft / campus solutions environments at various bundle levels and we are using load balancing / SSL via a Big IP system. SSL is terminated at the load balancer and we have a certificate on there but not.

I can log in fine to all the environments that have been configured this way, and can get reports to post to a dedicated psreports for each environment by entering the direct http URL of the web server when configuring the report node. However, when I try to view a report that has posted, I have to log in again. If I use the https address, it complains about certificates, because there is no certificate on the web server (only on F5) and we want it to stay that way. How do I configure my report nodes so that (a) reports post successfully and (b) I can access them without the need to log in again.

I have read elsewhere on toolbox that peoplesoft doesn't support load balancing of report servers, and that I should use a single reporting web server and a shared psreports location. However, I just don't know what I have to do to make this work. Can anyone provide 'dummies' steps for me please. Eg do I have to set up a new PIA and a web site under that for each environment (with http rather than https addresses?) and corresponding psreports folder? What do I then put in the various fields on the report node configuration. Thanks in advance Julie '. Julie, in URL on report node definition, you would be giving your URL (as per the virtual addressing/URL rewrite) and in the URI Host and URI Port you have to give the details of your primary site (IP/Machine Name and Port), there is no way of automated failover.

Here, there is a problem if you configure individual psreports directories. Suppose you have 4 web servers and you have configured URI Host and URI port of the first server.If your session is sticked to server 4 but you want to open the reports, then it would throw a could not display error as the report is not present in the report repository of the 4th server. So, I would recommend a Network Share for psreports folder and a manual switch of URI Host/URI Port (along with Process Scheduler bounce) whenever primary site goes down. Thanks Nithin for all your help. I have now managed to get my reports working correctly. It was the URI host/port that I didn't have correctly.

Behavior of Shared Fields The following fields are shared between the Http Distribution Node page and the FTP/XCopy Distribution Node page: • URL • Description • Operating System • Login ID • Password • Confirm Password When you enter information on one page, the information also appears in the shared fields on the other page, but the fields are unavailable. If you complete the information for one protocol and then change your selection to another protocol, the shared fields become active on the other page and unavailable on the original page. Upon saving, the system automatically clears fields that are not shared. File Chunking The Distribution Agent automatically breaks up a large file and sends it in multiple HTTP posts.

For example, a 150-MB file can be sent in 10 × 15 MB, 15 × 10MB, and so on. To accommodate different hardware configurations (memory) and dissimilar Java Virtual Machine (JVM) tuning, two new parameters have been added to the PeopleSoft Process Scheduler section of the configuration file (prcs.cfg): • Chunking Threshold • File Chunk Size These parameters enable clients to determine the most favorable configuration for their systems by trading off between the number of hits to the Web server when sending small chunks and memory usage due to sending large chunks.