Publishing webservices to the Internet through ISA 2006

Wigi
Member Posts: 13
Hello,
I have a question about webservices.
Using the URL http://servername:7047/name/ws/services gives a proper respons, so the services work correctly.
Our developers want to use the webservices to publish specific data.
The next step we want to do is publish the result to the Internet so that the data can be accessed through the Internet.
Where I get stuck is how to configure ISA 2006 so that the data can be published on the Internet. Does anyone have experience with this subject and would you like to enlighten me?
Help would be very much appreciated.
Kind regards, Wim.
I have a question about webservices.
Using the URL http://servername:7047/name/ws/services gives a proper respons, so the services work correctly.
Our developers want to use the webservices to publish specific data.
The next step we want to do is publish the result to the Internet so that the data can be accessed through the Internet.
Where I get stuck is how to configure ISA 2006 so that the data can be published on the Internet. Does anyone have experience with this subject and would you like to enlighten me?
Help would be very much appreciated.
Kind regards, Wim.
0
Comments
-
Hi,
it should work like http://msdn.microsoft.com/en-us/library/gg502476.aspx, but with ISA You should remember that the published servername can be different from Your NAV-Server.
Volker0 -
Hi Volker,
thank you for your reply. But we don't want to publish to an RTC client, but make the data (xml stream), generated by a webservice, available on the internet for an VB application, a web-site of any other program designed to call the webservice.
My problem is how to make the internal webservice available to the Internet through ISA 2006.
Kind regards,
Wim.0 -
Solution:
In ISA MMC click with the RMB on Firewall policy and choose New > Non-Web Server Protocol Publishing rule…
Enter a name for the rule. Click Next.
Enter the internal IP adress of the server where the webservice is configured. Click Next.
Select a protocol or create a new protocol by clicking on New.
Enter a name for the protocol.
Make a new primary connection by clicking on New.
Enter the desired criteria, in this case: TCP, Inbound, From 7047, To 7047. click OK.
This data will be stored under Primary Connection Information opgeslagen. Click Next.
A Secondary Connection is not needed. Click Next.
A summary of the new protocol will be shown. Click Finish.
The values of the protocol will be added to the Publishing rule. Click Next.
Select a Network listeners. Click Next.
A summary of the new Publishing rule will be shown. Click Finish.
The eternal URL will be something like:
http://www.xxxxx.com:7047/servicename/W ... tionImport
To open the URL and have the data displayed a username and password need to be entered.
The username must have limited to no access on the network and needs read and write permission in the database.0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions