“a java based code in mainframes”
At the most primitive of levels, what you have is the following
A=Create Socket
Open Socket (A)
Send on Socket(A) some request
Receive on Socket(A) some response
Close Socket(A)
So, at the most primitive level, you could use windows sockets to produce and deliver load though a remote API interface. But your application service residing on the mainframe might have a more robust interface that it can take advantage of, so moving up the OSI stack…
For a presentation layer view, perhaps a C level API exists, something that you can load a DLL for a Windows user and be able to affect remote procedure calls to the API on the mainframe. You could potentially use either a C template virtual user or a roll your own in Visual Studio type of virtual user
For an application layer view, perhaps there is a Java client complement, thinking in the CORBA-context. In such a case you may be able to leverage existing Java code for a Java template virtual user.
Three potential access models, Winsock, C Template (with client API code to the mainframe based Service interface) | DLL Virtual User in Visual Studio, or Java Template.
James Pulley, http://www.loadrunnerbythehour.com
--
You received this message because you are subscribed to the Google
"LoadRunner" group.
To post to this group, send email to LR-Loa...@googlegroups.com
To unsubscribe from this group, send email to
LR-LoadRunne...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/LR-LoadRunner?hl=en
It’s not a terminal, it is a service running on the mainframe