More questions about DI Server

[Former Member]

Now we finally got the link to the DI Server help file, for which I am most grateful.

However, the help file raises as many questions as it answers. I am somewhat familiar with the basics of creating and consuming web services. Still, after reading through the help file, I can't quite figure out the details of how to actually call the services provided by the DI Server.

For instance, I would like to make calls to the DI Server with a tool like wfetch or web services studio, but I have no idea which IP port and path the DI Server listens to (80?), if this could be configured or not etc. etc.

I guess the sample VB project WSClient.vbproj - which was mentioned in the help file - would reveal the necessary details, but unfortunately it didn't follow with the installation files.

Is there anybody out there actually already using the DI Server who could help us mortals with some implementation details ?

Best Regards,

Henry Nordstrom

[Former Member]

Hello Henry,

I am starting to work with DI-Server.

I don't have the WebSAPManageSoap.asp file.

I want to test the connection to the Database with XML.

Can you send me this ASP file?

Best Regards,

Willem van Eekelen

willem.van.eekelen@jamin.nl

[Former Member]

Hello Henry,

Thanks for your contribution; I'm going to test these files but I'm also using a 2003 server with IIS..

So it will probably fail also....

Jerome

[Former Member]

I got some answers to my questions during a SBO 2004 SDK workshop, which was held this week. I'm posting them here just in case someone else has faced the same questions.

- you need to be have Internet Information Server installed and running

- you can check if the DI Server is correctly configured and working by opening the path

http://127.0.0.1 (or http://localhost) with a web browser.

What you should see then is a simple html form which has a text field for inserting a SOAP request.

At least in my installation, this did not work 'out of the box'. I needed to manually add three files under the \inetpub\wwwroot folder:

default.htm

global.asa

WebSAPManageSoap.asp

...I got these files directly from a representative of the SDK dev team. I guess they will be included in future installation packages of DI Server.

Regards, Henry

[Former Member]

Henry do you have a copy of these files?

I am using webservices running IIS on the same box as SBO. I am running into some errors using some objects within the DI API on the Windows Server 2003 platform, however if I run the application on an XP PRO box and point my company object at SBO installation on 2003, the same objects will work fine.

Apparantly this has something to do with 2003 tightened security, I tried using impersonation, but this still did not work...

Does anyone know how to get round this 2003 COM secuirity?

[Former Member]

Hello Henry,

Could you send me these files you got from SAP, please ?

I would want to test it ou the box.

Which development environment do you use to develop web services ?

I'm interested in any information you have about development with DI server...

my email is jerome.munier@2moro.fr

Thanks very much

Jerome

Message was edited by: jerome Munier

[Former Member]

Hi,

There are two files required in the www root folder of the IIS: Global.asa and WebSAPManageSoap.asp. Additionally, you will need a simple html file as a launchpad for the SOAP requests.

Here are the contents of the three files:

= = = Global.asa = = =

<SCRIPT RUNAT=Server LANGUAGE=VBScript> Sub Session_OnStart Session.Timeout = 1 Set Session("SBODI_Server") = Server.CreateObject ("SBODI_Server.Node") 'Set Session("SBODI_Server") = Server.CreateObject ("Com2Corba.Nodec") End Sub Sub Session_OnEnd set Session("SBODI_Server") = Nothing End Sub </SCRIPT> = = = WebSAPManageSoap.asp = = = <% 'connect to the database and perform the search dim requestStr dim outStr dim obj requestStr = Request.Form.Item("HTTP_SOAPACTION") set obj = Session("SBODI_Server") outStr = obj.Interact(requestStr) Response.Write outStr Response.End %> = = = default.htm = = = <HTML> <HEAD> <META NAME="GENERATOR" Content="Microsoft Visual Studio 6.0"> <TITLE></TITLE> <SCRIPT ID=clientEventHandlersJS LANGUAGE=javascript> <!-- function button1_onclick() { } //--> </SCRIPT> </HEAD> <BODY> <form method=post action="WebSAPManageSoap.asp"> <INPUT language=javascript id=button1 style="WIDTH: 84px; HEIGHT: 24px" type=submit size=36 value=Submit name=button1><TEXTAREA id=HTTP_SOAPACTION style="WIDTH: 800px; HEIGHT: 393px" name=HTTP_SOAPACTION rows=5 cols=46>Put soap request here</TEXTAREA> </form> </BODY> </HTML>

= = = end = = =

Now I have made a similar installation on a Windows 2003 Server. On this installation, the system does not seem to work with these files. IT seems that the SOAP calls are not reaching the DI Server at all, as the DI Server log now only contains information about starting and stopping the DI server. This is what I keep getting in the IIS log file:

2005-01-12 12:46:13 127.0.0.1 GET /default.htm - 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 200 0 0

2005-01-12 12:46:24 127.0.0.1 POST /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:47:21 10.169.32.4 OPTIONS / - 80 - 10.169.32.72 Microsoft-WebDAV-MiniRedir/5.1.2600 200 0 0

2005-01-12 12:47:21 10.169.32.4 PROPFIND /Data - 80 - 10.169.32.72 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 0

2005-01-12 12:47:21 10.169.32.4 PROPFIND /fijhsk00$ - 80 - 10.169.32.72 Microsoft-WebDAV-MiniRedir/5.1.2600 501 0 0

2005-01-12 12:47:50 127.0.0.1 POST /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:47:52 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:47:52 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:47:52 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:47:53 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:47:53 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:50:23 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:50:25 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:50:25 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2005-01-12 12:50:26 127.0.0.1 GET /WebSAPManageSoap.asp |13|800a000d|Type_mismatch:_'Session' 80 - 127.0.0.1 Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.2;.NETCLR+1.1.4322) 500 0 0

2

= = =

Has anyone got a clue what might be wrong with the installation ?

Henry