I made a CRUD web application in netbeans ide.
When I add an entry from another machine the change is not reflected on this machine.
I made change from 192.168.0.19:8080/appname on another computer and the change is not relected on localhost:8080/appname. Glassfish server is run on localhost.
Need to test this but maybe because I'm sending to the same port on different machines? Should I try with port 8181?
Im thinking since I autogenerated it the app wont support AJAX?
Update works if I hit return as soon as I added a record in another machine, or if I add a new record. So the solution should involve auto-refreshing the page in a time interval.
Set up primefaces and tried this in xhtml
<p:poll interval="10" listener="#{phonerecordController.listener}" update="#all" />
But I'm not sure which method should be the listener.
<p:poll interval="10" listener="#{phonerecordController.preparelist}" update="#all" />
Set up primefaces then put the above code inside xhtml and it worked.
Related
i have problem with project deployment, so the application appear just if I put the port of the server like screen,s I use "angular" "expressjs" "ovh"
the error
here i need to put the port to appear the app
I inherited an existing project without its development environment. I have UAT code and a backup of the Production database. I can run up the site locally via Visual Studio but have hit an authentication problem trying to setup a fresh standalone DEV server on AWS (single server, no load balancer). The doco indicates the Prod server is a dual server setup with a load balancer.
The front end site pages do display, although some search is not working. On trying to log into the backend pages, Chrome returns "The xxx page isn't working. xxx redirected you too many times." Using developer tools, I can see the page redirects back and forth between SWT?realm=... and sitefinity?wrap_defalted=true&wrap_access_token... On the second redirect response header there is "X-Authentication-Error:Missing configuration for the issuer of security tokens 'https://xxx/Sitefinity/Authenticate/SWT' "
I tried different values in the web.config lines:
<federatedAuthentication>
<wsFederation passiveRedirectEnabled="true" issuer="http://localhost" realm="http://localhost" requireHttps="true"/>
<cookieHandler requireSsl="false"/>
</federatedAuthentication>
but that actually made things worse so I have reverted.
I checked all the settings mentioned in http://docs.sitefinity.com/administration-switch-to-claims-based-authentication and they seem to be set correctly. I don't really know what else I can check to get this working.
I found http://docs.sitefinity.com/administration-configure-security, but it does not seem like these settings are set (I don't have access to Prod server so can't confirm if it is actually setup with load balancing). I am currently using a 30 day trial license so am not sure if this is contributing to the problem. The official license is in the process of being transferred by the client. The domain name associated with the official license would be different to the domain my new server is currently running on.
I am also running version 8 code on a version 9 install of Sitefinity. I wanted to get it working before I tried to upgrade the code. I think there was also an assembly load to manifest mismatch when I tried upgrading my local version.
Found the solution: Don't mess with the SecurityConfig.config file.
<securityTokenIssuers>
<add key="B886AA7BFB5515BA63F577A44BBEB5C7AE674035514D128BC397346B11F4C97A" encoding="Hexadecimal" membershipProvider="Default" realm="http://localhost" />
</securityTokenIssuers>
<relyingParties>
<add key="B886AA7BFB5515BA63F577A44BBEB5C7AE674035514D128BC397346B11F4C97A" encoding="Hexadecimal" realm="http://localhost" />
</relyingParties>
Even though it is running on a server, the above lines should still point to localhost. It seems like these only need to be edited if you have a multi-server setup with an entirely separate STS.
I initially changed it to match the new domain name, but after some experimentation around adding localhost and HTTP variations, it seems like it works best with just localhost.
Even when I changed the web.config entry above to use the new domain as the issuer instead of localhost and the SecureConfig.config to specify only the new domain as the realms, it didn't seem to work. I guess the authentication must try to hit localhost specifically.
Our ServiceNOW instance recently got upgraded from Eureka to Geneva.
MID Server status became down and the version does not match the Build number in the stats.
I was told that the MID Server will auto upgrade which didn't happened. I am using a proxy server to connect, when I tried communicating with the instance through the server it is working however I assume the service or application installed is not able to communicate with the instance.
I created a new service and it worked perfectly for 1 min however after that the status of it became down.
Then I tried changing the configurations of old services however no good.
Now the services are running fine however in the config file in the mid_sys_id section mid server details not getting populated and the status of the MID Server in the instance is always down.
Do I need to change any properties in the instance?
Since I use proxy server do I need to remove the comment line of the auto upgrade through proxy section or can I leave that blank?
What is the issue here? Why my MID Server is not getting upgraded? Kindly help me.. If possible an explanation with screen shot would be much appreciated.
If you're on Geneva, you should be able to simply go to your MIDServer listing, from inside your instance, click on a MIDServer, and find 'Upgrade MID' in the Related links section. That should start an upgrade for that MID Server. If it fails, there should be an entry in either the ServiceNow logs or the MID Server logs with more information why it failed.
I have some problem and trying to solve for a few days..
I installed iis 6.0 but I updated it 7.5 express and 7.0. it looks 7.5 version..
so, I published wcf to localhost and set 4501 port. I can see file when I run iis http://localhost:4501/
but svc file doesnt work. When I click or type http://localhost:4501/Products.svc it doesnt work and I see a blank website.. nothing..
But If I run svc client in visual studio, asp.net development server works and my svc file works.. (http://localhost:4501/Products.svc) everything is same..
I dont understand why IIS doesnt work well?
I think that 6.0 doesnt support .. I use a proxy and I can connect to my global ip with proxy or my friend opens it.. but still svc file doesnt work..
I think the problem is iis.. but a global side, asp.net development server doesnt work too, but it works on localhost..
I opened all ports, add some new rule to firewall and i closed firewall (modem and computer)
I really become a crazy..
Edit: I try to connect ip with http://myGlobaLIp:4501 I can see my files on my localhost but If I try http://myGlobalIp:4501/Products.svc I get blank page..
Here is your issue: when you run from Visual Studio it automatically runs a virtual IIS for you, and assigns the ip/port...in this case it's http://localhost:4501/. When you setup the site and run it in IIS, you have to set those values during the website setup.
You need to create a website in IIS, then point to your code (publish it to a location like c:\inetpub\wwwroot\myapp)
You then need to set which port your webservice should run on.
THEN, go to http://{your ip or machine name}:{port configured in IIS, not the VS virtual IIS port}/Products.svc
Here is a step-by-step walk through from Microsoft to help you deploy a website (or wcf webservice): http://technet.microsoft.com/en-US/library/f6c26eb7-ad7e-4fe2-9239-9f5aa4ff44ce.aspx
good luck
I am trying to deploy a simple "Hello World" .NET 4.0 REST-style WCF service on WinXP (IIS5). It works fine in Cassini.
I tried to adapt the info here to me:
http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx
but something is not clicking. Can anyone lend ideas or comments? Yes, I must stay with WinXP.
Thanks.
After a fair amount of struggling I was able to successfully deploy a WCF 4.0 REST web service on XP/IIS5. For the benefit of you and others in the same situation, here's what I did (let me know if you need more detail):
Using VS 2010, build a deployment
package for the project and then
install it on the target machine
(your web server). The following
link will show you how to do this: http://vishaljoshi.blogspot.com/2009/03/web-packaging-installing-web-packages.html
Make sure that your virtual directory in IIS is configured to use .NET 4 (right click on virtual directory > properties > ASP.NET tab > ASP.NET Version)
Configure your virtual directory to support extensionless requests (i.e. your REST API) by creating a wildcard mapping (right click on virtual directory > properties > configuration > mappings tab) with the following properties:
Executable: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll
Extension: .*
Check that file exists: unchecked
(Note: watch out for the bug that keeps the "OK" button on this dialog grayed out. To get around this just click in the executable textbox after entering your extension and the "OK" button should get enabled).
If you get an authentication error when accessing the service then turn off integrated authentication on the virtual directory. This should fix the problem if you have used the defaults in the generated web.config of your service. If you have explicitly modified the authentication mode then you will have to adapt accordingly.
Have you considered self-hosting your service instead of trying to use IIS. That will probably be easier to do than use IIS.
In case above steps dont work. There could be a problem with permissions on your App pool for that website / virtual directory , you can try to set that right and try it out.
You can refer this article for more help on this.
http://technicalwizardry.blogspot.in/2013/04/wcf-rest-service-hosted-on-iis-5.html#!/2013/04/wcf-rest-service-hosted-on-iis-5.html