I want to change the host value with my IP address when i connect to wifi, but when I build the app it is still localhost.
How to change server host?
To change the host address of your Worklight Development Server:
Open the Servers view in Eclipse (if you don't see if, press Ctrl+3 and search for "servers")
Double-click on "Worklight Development Server"
Change the Host name value from "localhost" to the IP address
In eclipse click on menu "Window->Show View->Servers" to display the worklight development server. If "Show View" does not display "Servers" view then click on "Other" option and search for "server" keyword.
Related
FWLPL0010W: "localhost" was detected from the target server
configuration. Using the primary IP address of the host machine,
197.255.122.78, to build the Worklight application(s). Consider using a fully qualified hostname (avoid using "localhost") or a valid IP
address instead. The value can be modified by opening the
configuration editor of Worklight Development Server from the
"Servers" view.
[2015-01-10 12:34:11]
com.worklight.studio.plugin.nls.Messages:FWLPL0001W: Server not
started yet. Build may fail at first trial. [2015-01-10 12:34:11]
FWLPL0017E: Worklight Console can not be opened because the Worklight
Server is not running. Right-click the server 'Worklight Development
Server' from "Servers" view and select "Start" from the menu to start
the server.
From the comment, the issue appears to be the following:
Server Worklight Development Server was unable to start within 120
seconds. If the server requires more time, try increasing the timeout
in the server editor.
A Google search brought up the following same question: Worklight Server not starting
The solution was provided per the instructions in http://www-01.ibm.com/support/docview.wss?uid=swg21668175:
To resolve this problem, you can apply one or both of the following workarounds.
Complete the following steps to increase the timeout default value:
1.Open the Servers view.
2.Double-click the Worklight Development Server to open the Overview pane.
3.Expand the Timeouts section.
4.Increase the value in the Start (in seconds) field. Consider doubling the default value; that is, set it to 120 seconds.
Complete the following steps to remove the unnecessary applications from Worklight Development Server.
1.Open the Servers view.
2.Right-click the Worklight Development Server.
3.Select the Add and Remove option.
4.Remove all applications that you do not intend to work on.
After you have made any of these changes to the configuration, restart the server.
I have a website that access a sql database in localhost and it works, but when published in an Azure website, can't reach the database. I've changed the connection string with visual studio on line pointing to a new database created in Azure, but can't reach the database.
There is a way to track the error? because the application only returns to the same webpage (this is the caondition when the connection to the database fails.
Any suggestion?
Check that the Azure firewall has a rule for the IP address of the machine hosting the website. You can do that by either of two methods:
Navigating to your Azure Portal using a browser that is on the same machine that is trying to access your database.
Go to the 'SQL Databases' section and click on the database.
In the 'Design your SQL database' section, click on 'Set up Windows Azure firewall rules for this IP address'.
If the machine already has a rule the portal will indicate that. Otherwise a new rule will be added.
The other way:
From the Management Portal, click SQL Databases. All databases and their corresponding servers are listed here.
Click Servers at the top of the page.
Click the arrow beside the server for which you want to manage firewall rules.
Click Configure at the top of the page.
To add the current computer, click Add to the Allowed IP Addresses.
To add additional IP addresses, type in the Rule Name, Start IP Address, and End IP Address.
To modify an existing rule, click any of the fields in the rule and modify.
Click Save at the bottom of the page to save the changes.
How to: Configure Firewall Settings (Azure SQL Database)
I am done with my Project and its time to Deploy things to the Websphere Server to host My Worklight Application based on Woklight 6.1.0.
Despite reading the following question, I still have a question.
IBM Worklight - How to connect to another Worklight Server located in another machine in the same network?
The Websphere Server on which i have to Deploy my .war, .wlapp and .adapter files is remote server and does not fall under my company's domain. I do not have access to IP address and port provided by clients, So to deploy the same my backup plan is to copy files to a laptop having open network access and use RDP of the Window Server IP to deploy
My issues are:
As Worklight behaves, while i do Run as --> Run on Worklight Development Server it overwrite file properties like worklight.properties,.plist and index.html for windows with details of its local IP address.
When i do, Run --> Build Settings and Deploy Target I build the application to work with different Worklight Server and fill details i.e. Server: http: //182.19.xx.x0:9xx0 and Context Path: /Advisor. After doing it i see a message stating "Rebuild your Application after every change" then i click on 'OK'.
I expected it to rebuild everything for me as per details i provided but nothing happens. Is there anything i am missing?
After you add your remote server details in the Build Settings and Deploy Target window, you are instructed to re-build the application. Worklight Studio will not do this for you.
Change deployment target
Click OK
Right-click on the application folder and select Run As > Build All Environment
Per the user documentation:
Important: This dialog is used only to specify configurations and
settings; clicking OK does not trigger a build. Any time that you make
a modification with this dialog, you must rebuild your application and
environments for your changes to take effect, using either the Run As
-> Run on Worklight Development Server or the Run As -> Build... menu commands.
I need to allow remote connections in SQL Server 2012 Express, the problem is that I am following every tutorial but without luck. The Microsoft tutorial and every one that I have been reading have sections that I don't have in my SQL Server Configuration Manager.
The msdn tutorial says this:
In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, expand Protocols for , and then double-click TCP/IP.
In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you want to configure.
If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.
In the IPn Properties area box, in the TCP Port box, type the port number you want this IP address to listen on, and then click OK.
In the console pane, click SQL Server Services.
In the details pane, right-click SQL Server () and then click Restart, to stop and restart SQL Server.
I don't have a SQL Network Configuration and the data I have is not the same.
This is how is my configuration right now (I don't know why says SQL Server 2005 Services, it does have anything in that section).
This is what I have installed on my pc (Windows 8.1 x64)
Finally thanks to #marc_s i founded that the SQL Server Configuration Manager was 2005 version and the 2012 version was not in start menu, so i searched manually and got it working now.
I want to connect from home using SQL Server 2005 to another PC.
I had a look on the msd...but before connecting it says I should connect to another computer
using the computer management and it didn't work out....I can only connect to computers from my workgroup?
Thanks,
Luisa
Disclamer
This is just some additional information that might help anyone. I want to make it abundantly clear that what I am describing here is possibly:
A. not 100% correct and
B. not safe in terms of network security.
I am not a DBA, but every time I find myself setting up a SQL Server (Express or Full) for testing or what not I run into the connectivity issue. The solution I am describing is more for the person who is just trying to get their job done - consult someone who is knowledgeable in this field when setting up a production server.
For SQL Server 2008 R2 this is what I end up doing:
Make sure everything is squared away like in this
tutorial which is the same tutorial posted above as a solution by "Dani" as the selected answer to this question.
Check and/or set, your firewall settings for the computer that is hosting the SQL Server. If you are using a Windows Server 2008 R2 then use the Server Manager, go to Configuration and then look at "Windows Firewall with Advanced Security". If you are using Windows 7 then go to Control Panel and search for "Firewall" click on "Allow a program through Windows Firewall".
Create an inbound rule for port TCP 1433 - allow the connection
Create an outbound rule for port TCP 1433 - allow the connection
When you are finished with the firewall settings you are going to want to check one more thing. Open up the "SQL Server Configuration Manager" locate: SQL Server Network Configuration - Protocols for SQLEXPRESS (or equivalent) - TCP/IP
Double click on TCP/IP
Click on the IP Addresses tab
Under IP1 set the TCP Port to 1433 if it hasn't been already
Under IP All set the TCP Port to 1433 if it hasn't been already
Restart SQL Server and SQL Browser (do both just to be on the safe side)
Usually after I do what I mentioned above I don't have a problem anymore. Here is a screenshot of what to look for - for that last step:
Again, if someone with more information about this topic sees a red flag please correct me.
If you want to connect to SQL server remotly you need to use a software - like Sql Server Management studio.
The computers doesn't need to be on the same network - but they must be able to connect each other using a communication protocol like tcp/ip, and the server must be set up to support incoming connection of the type you choose.
if you want to connect to another computer (to browse files ?) you use other tools, and not sql server (you can map a drive and access it through there ect...)
To Enable SQL connection using tcp/ip read this article:
For Sql Express: express
For Sql 2008: 2008
Make sure you enable access through the machine firewall as well.
You might need to install either SSMS or Toad on the machine your using to connect to the server. both you can download from their's company web site.
all of above answers would help you but you have to add three ports in the firewall of PC on which SQL Server is installed.
Add new TCP Local port in Windows firewall at port no. 1434
Add new program for SQL Server and select sql server.exe
Path: C:\ProgramFiles\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\sqlservr.exe
Add new program for SQL Browser and select sqlbrowser.exe
Path: C:\ProgramFiles\Microsoft SQL Server\90\Shared\sqlbrowser.exe
I'll edit my previous answer based on further info supplied. You can clearely ping the remote computer as you can use terminal services.
I've a feeling that port 1433 is being blocked by a firewall, hence your trouble. See TCP Ports Needed for Communication to SQL Server Through a Firewall by Microsoft.
Try using this application to ping your servers ip address and port 1433.
tcping your.server.ip.address 1433
And see if you get a "Port is open" response from tcping.
Ok, next to try is to check SQL Server. RDP onto the SQL Server computer. Start SSMS. Connect to the database. In object explorer (usually docked on the left) right click on the server and click properties.
alt text http://www.hicrest.net/server_prop_menu.jpg
Goto the Connections settings and make sure "Allow remote connections to this server" is ticket.
alt text http://www.hicrest.net/server_properties.jpg
Here is the link ... You must read it.