HTML5 website to Tandem

[William, Lin]

Folks,

This is very 'open' questions for you , about to develop a HTML5 based web page to interact with tandem machine (like pathway or tandem based webservice)

I want to hear your thoughts of what technologies we can use and how will the tech architecture look like?


Thanks

[Anupam Das]

If you choose to use your existing Pathway servers for your application without using Web-services, you will go via iTP Webserver and then a Pathway CGI script and then to the actual Pathway server-class.

If you choose to use your existing Pathway servers via SOAP, then you will go via iTP and then NS-SOAP server and then to your actual Pathway server-class.

[Anupam Das]

>> you will go via iTP Webserver and then a Pathway CGI script and then to the actual Pathway server-class. <<

Sorry! Not necessary to have a Pathway CGI script always in the middle. This is only necessary when you would choose to NOT to touch anything in your existing Pathway server program.

[Robert Hutchings]

Hi William...

NonStop SOAP is based on Apache Axis 2

http://axis.apache.org/axis2/java/core/

Long story short, you can invoke NonStop services via iTP Web server, as Anupam said. iTp is also based on Apache (web-server).

I would have to research the NonStop manuals if you need RESTful web services...

[Robert Hutchings]

Check here for Open Source on NonStop info...
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03562221/c03562221.pdf

[Bill Honaker]

I used to think iTP was based on Apache, but was corrected a few years
back by somoen in the know. Configuration is similar to apache but
many Apache 'features' don't exist (mostly because they aren't needed,
since iTP (running on NonStop) works fundamentally different).

NS/JSP is based on Tomcat and many HTML5 tools that rely on that and
AXIS should run well.

As always, some packages that depend on multiple threads running in a
shared memory space will not scale well and should be investigated on
a case-by-case basis.

[William, Lin]

在 2013年7月3日星期三UTC+8下午7时42分28秒，William, Lin写道：

> Folks, This is very 'open' questions for you , about to develop a HTML5 based web page to interact with tandem machine (like pathway or tandem based webservice) I want to hear your thoughts of what technologies we can use and how will the tech architecture look like? Thanks

Thank you guys these are helpful

It sounds to me that the webserver should run at NonStop. Is it possible that we run the webserver at PC and have this webserver interact with NonStop (like pathway, processes ? )

Thanks

[Robert Hutchings]

The iTP webserver runs on the NonStop server only. This is how you gain access to NonStop services. There are many other way to access NonStop like ODBC, JDBC, Remote Server Call, Tuxedo, MQ, etc.

Running a webserver on your PC would not have anything to do with the NonStop...

[Anupam Das]

>> Is it possible that we run the webserver at PC and have this webserver interact with NonStop (like pathway, processes ? ) <<

Which webserver?

If you use IIS(as you said PC, I presume Windows running on there), then you could access Pathway via RSC/MP, SOG, CSL, NuWave SOAP/AM etc.

If you use Apache, then may be you would use PHP script or some form of CGI script to access NonStop? I didn't do that yet. May be someone here has tried.

[Robert Hutchings]

Yes, Anupam is right. I suppose you could connect your PC webserver to NonStop iTP webserver. Maybe if we knew what you need (more detail), we could help more...

[William, Lin]

在 2013年7月4日星期四UTC+8下午11时02分25秒，Robert Hutchings写道：

> Yes, Anupam is right. I suppose you could connect your PC webserver to NonStop iTP webserver. Maybe if we knew what you need (more detail), we could help more...

I'm going develop HTML5 based webpage which can access pre-existing pathway servers at tandem and also access (directly) some files at tandem. In this HTML5 web, i'm looking for a 'PUSH' availabilities from server to front-end.

The iTP webserve may be a good choice for this, but i'm seeking another way , to have the webserver running at PC (I'm thinking that iTP doesn't support 'webSocket' which is new feature of HTML5 to make 'PUSH' function easier)

Thanks

[Anupam Das]

>>
The iTP webserve may be a good choice for this, but i'm seeking another way , to have the webserver running at PC (I'm thinking that iTP doesn't support 'webSocket' which is new feature of HTML5 to make 'PUSH' function easier)
<<

In that case, use install SOAP on NonStop and you should be done.

[Robert Hutchings]

You might also check out NonStop JSP...you might be able to use JPathsend or JToolkit.

[Robert Hutchings]

Check here:

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02132555/c02132555.pdf

[Anupam Das]

>> You might also check out NonStop JSP...you might be able to use JPathsend or JToolkit. <<

Rob, I have a question as I myself didn't experiment with NSJSP much. OP just wants to reach a Pathway server-class from another machine. Won't JSP bring another overhead of coding servlet-serverclass etc in the middle? I am just checking. I even didn't recommend him using Pathway CGI scripting because that is still a coding effort in my opinion. Contrary to that, NS-SOAP is all about configuration, no coding effort required to reach up to traditional servers.

[Robert Hutchings]

Hi Anupam,

I think you are right as far as the amount of effort. Using JSP would introduce more coding (I think) and perhaps more "layers" of technology. SOAP or SOAP-AM
(http://blog.ticsoftware.com/blog-0/?Tag=Attunity) might be easier for the OP.

The main thing is to access the Pathway servers as easily as possible. JSP is a whole technology in and of itself. I mentioned it because I think it gets you access to Java on NonStop, and from there your could access Pathway with JPathsend/JToolkit. If the OP is Java-oriented this might be a good solution.

[Anupam Das]

>>
SOAP or SOAP-AM (http://blog.ticsoftware.com/blog-0/?Tag=Attunity) might be easier for the OP.
<<

Oh yes! I completely forgotten about this product. If OP's application runs from Guardian space, then it would make more sense to go for SOAP/AM product instead of installing OSS and then iTP and then NS-SOAP etc. Additionally, a closer look at the SOAP/AM product will reveal another advantage - this SOA product does not depend on another web-server to function. It has it's own inbuilt and customized Web-server that understands HTTP request. So, Web-server and SOAP server basically runs as a single binary and there is NO messaging between these two components :-).

[William, Lin]

在 2013年7月7日星期日UTC+8下午5时21分44秒，Anupam Das写道：

> >>
>
> SOAP or SOAP-AM (http://blog.ticsoftware.com/blog-0/?Tag=Attunity) might be easier for the OP.
>
> <<
>
>
>
> Oh yes! I completely forgotten about this product. If OP's application runs from Guardian space, then it would make more sense to go for SOAP/AM product instead of installing OSS and then iTP and then NS-SOAP etc. Additionally, a closer look at the SOAP/AM product will reveal another advantage - this SOA product does not depend on another web-server to function. It has it's own inbuilt and customized Web-server that understands HTTP request. So, Web-server and SOAP server basically runs as a single binary and there is NO messaging between these two components :-).

Thank you Anupam

[William, Lin]

在 2013年7月6日星期六UTC+8下午10时51分26秒，Robert Hutchings写道：

Thank you Rob and all of you!

[Robert Hutchings]

You are quite welcome William. Hope we helped.