tag:blogger.com,1999:blog-31216575.post2948655503781990233..comments2024-01-27T07:32:53.464+01:00Comments on On The Peoplesoft Road: On The Peoplesoft Road : Application ServerNicolas Gasparottohttp://www.blogger.com/profile/06634519580752248909noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-31216575.post-91961425455418341012011-04-04T22:25:31.004+02:002011-04-04T22:25:31.004+02:00Hello Rajkumar,
I had the same problem and ran nm...Hello Rajkumar,<br /><br />I had the same problem and ran nmap. Port 7000 (the default workstation listener port) was open when it was run on the server, but was not open when run on the client and pointed at the server. The firewall was disabled so that was not the issue. I am running Peoplesoft on VMware using a NAT connection. This problem was solved by modifying psappsrv.cfg<br /><br />[Workstation Listener]<br />;======================<br />;Settings for Workstation Listener<br />;===============================<br /><br />;Address=%PS_MACH% comment out this line and replace with this<br /><br />Address=//000.000.000.000<br /><br />; where 000.000.000.000 is the IP address of your virtual machine<br /><br /><br />After doing this and reconfiguring the domain through psadmin I was able to connect with Application Designer and nVision in 3 tier mode.<br /><br /><br />ToddAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-31216575.post-66837808367463289592010-06-18T21:28:59.032+02:002010-06-18T21:28:59.032+02:00Hello i have the same problem. i can't connect...Hello i have the same problem. i can't connect to the application server with the application designer . I'm using the port 7000.<br />How can i check if the application server is correclty started?<br /><br />GillesAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-31216575.post-23322058473721202082010-05-14T07:41:58.625+02:002010-05-14T07:41:58.625+02:00The file name is configuration.properties ( in cas...The file name is configuration.properties ( in case of web logic).<br /><br />The pay may look like, $PS_HOME/weblogic/..../PORTAL/WEB-INF/psftdocs/FINPRO/configuration.propertiesAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-31216575.post-9520529853386594822010-05-14T07:37:31.800+02:002010-05-14T07:37:31.800+02:00Hi,
Please check if your port number is correct. ...Hi,<br /><br />Please check if your port number is correct. In this example, 7000 port was allocated to WSL. <br /><br />The web config file should have an entry psserver=HOSTNAME:PORT_NUMBER.<br />where, HOSTNAME is the computer where you configured the application server. And, the PORT_NUMBER is the JSL port number (not WSL port number).Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-31216575.post-26884218258159100632010-03-18T19:03:57.652+01:002010-03-18T19:03:57.652+01:00I am getting the same problem as Rajkumar.
"...I am getting the same problem as Rajkumar.<br /><br />"Could not connect to application server PT850//157.201.227.51:7000). <br />Possible causes are: the server name/IP address and port for the application server alias are incorrect, the application server is not booted, or the network is unreachable. Contact your system administrator or check the Tuxedo log for more information. "<br /><br />The WSL service is running and I can see it when I do a netstat. I can do an nmap for the localhost and see the port, but when I do an nmap to the machine: 157.201.227.51 port 7000 is not shown as open. I have checked the IPTABLES and it shows that port 7000 is open on the firewall. I have even tried shutting down the firewall but it mad no difference. <br /><br />I can ping the machine and connect directly to the database from the Windows client. <br /><br />I have tried everything I can think of. Can anyone help?Unknownhttps://www.blogger.com/profile/16044769617410314724noreply@blogger.comtag:blogger.com,1999:blog-31216575.post-52333401402861960392009-05-25T19:12:58.842+02:002009-05-25T19:12:58.842+02:00Jim, looks interesting.
Maybe you didn't set $ORAC...Jim, looks interesting.<br />Maybe you didn't set $ORACLE_HOME and not added the $ORACLE_HOME/bin into the $PATH variable in your .profile or .bash_profile (step 1+ disconnect+reconnect), did you ?<br />I never had to play with TNS_ADMIN and with a very local tnsnames.ora file of the PS user neither.<br />Furthermore, if many databases are managed on same server, it is maybe better to maintain only one tnsnames.ora (the one from $ORACLE_HOME/network/admin) instead of one by PS user, isn't it.Nicolas Gasparottohttps://www.blogger.com/profile/06634519580752248909noreply@blogger.comtag:blogger.com,1999:blog-31216575.post-65405840539857318772009-05-25T18:58:56.397+02:002009-05-25T18:58:56.397+02:00Nicolas, on step 2, I couldn't get signed into SQL...Nicolas, on step 2, I couldn't get signed into SQLPlus. I was getting the error "ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA." I copied $ORACLE_HOME/network/admin/tnsnames.ora to ~/hrms9/.tnsnames.ora and was able to connect. Of course, I could have set TNS_ADMIN to point to $ORACLE_HOME/network/admin.Jim Marionhttps://www.blogger.com/profile/12995110203807924786noreply@blogger.comtag:blogger.com,1999:blog-31216575.post-83579820549899572922008-11-14T23:44:00.000+01:002008-11-14T23:44:00.000+01:00hi,as per your method,idid all the installation pr...hi,<BR/><BR/>as per your method,idid all the installation procedure.. But coultn't connect application desiner ...i'm getting follwing error <BR/><BR/>"Could not connect to application server DELL (//172.168.10.200:7000). Possible causes are: the server name/IP address and port for the application server alias are incorrect, the application server is not booted, or the network is unreachable. Contact your system administrator or check the Tuxedo log for more information. "<BR/><BR/>Thsnks<BR/>RajkumarAnonymousnoreply@blogger.com