"How to debug ‘server side code’ in Powerbuilder” - powerbuilder

I have a powerbuilder application and it is 3 tier architecture. The business objects are written in server side. How to debug the server side scripts? I tried to insert the break point in the server side calling function from the client side script. But it is not step into the server side script.

I would try to instantiate the objects locally and debug them that way.


Weblogic add-on to serialize web service calls

Is there a prebuilt tool that would integrate with BEA/Oracle Weblogic 10.0 and trace on a database table each call to a web service exposed by the server?
UPDATE: the goal is not to debug the web services (they are working well). The objective is to trace each call on a table, using an existing add-on.
Yes, a remote debugger, like pretty much any modern IDE. Attach it to the running application server, breakpoint at the webservice entry point, and follow it through.
Not sure if there is an add-on, but you can write a handler (extends from javax.xml.rpc.handler.GenericHandler) where you can write logic to inspect (and manipulate if you so choose) the request, response and the fault (if it occurs). You can detect things like the remote ip, remote user, etc, and then do whatever you want with them ( i.e. log them to disk, console, db, etc)

Multiplayer Game Server Using deepsream

I get to know that we can use List to make different rooms/lobby over server. I am new to server side development. I am bit confuse now. Like i need to make list(rooms) at server side. So which module I'll use to make server side code ? should i code using node js module of deepstream . Currently i have just connected to deepstream server and also connected rethinkdb and redis cache connector. So do i need to write a separate node module to do server side coding using node deepstream.io-client-js ? or do i need to implement a server over deepstream.io module?
it would be a great help if anyone can tell
When using deepstream, the notion of 'server-side coding' is less clear than in traditional http-based applications. Usually the client will communicate directly with the deepstream server, and often application logic can be defined directly in the client. Security is then provided by configuring Valve permissions and authentication in the deepstream config.
For cases where application logic cannot be handled securely on the client, we recommend setting up Data Providers. Here, one or more 'provider' servers will run a deepstream client and provide access to a resource through deepstream's RPCs (remote procedure calls) or using the Active Provider pattern.

Publish a value of a C program to a webpage

I have built some sensors around my Raspberry Pi. With a C++ program, I can read out the SPI bus to get the sensor values. What i want to do now is to publish these values to a simple web page (php, html or whatever). I have installed LAMP on the Pi and successfully published a simple web page in my personal network.
So the 'only thing' that is left is to make a connection between an html page and my C++ program, but I have no idea how to do it. So the question is, am I on the right track, and how can it be done? I am not able to find a 'simple' solution and don't know where to begin.
You need to understand some of HTTP
You could make your C program a web server using some HTTP server library like e.g. libonion, mongoose (as commented by oysteijo), libmicrohttpd etc... (in C++ consider also Wt). Then your application would provide a web page.
You could make your C program a web client using some HTTP client library like libcurl. Then your application would e.g. fill a web form located elsewhere. (your C program could also e.g. be database client and some other Web server would access the same database and display the data).
You could also consider making your C program a CGI or FastCgi application (interacting with a web server like Lighttpd or Apache...)

Connect web server to another application [closed]

I'm interested in how I might send requests from a web server using Python to a constantly running C++ program. Basically users should be able to send "orders" via their browser to the web server. The web server then needs to forward those orders to a constantly running application written in C++. Eventually the C++ program should be able to send order results back to the web server who can forward the results to the user's browser if they're still connected.
I've thought about having the web server record pending orders to a database which the C++ program polls for changes. That doesn't seem very efficient though. I believe it will have issues with to many users. Is there some method/technology that is typically used for this type of situation?
You have a few options;
1. API
This is more the traditional option, you have some form of API built into your website, and your C++ program contacts the API to receive and update orders. You would probably want to use this if your C++ program isn't hosted on the same server. However you will need to ensure you keep the API secure from outside parties accessing it to fake orders etc.
2. Shared file or database
If your application is running on the same server you could have both programs access a database or flat-file.
3. Sockets (TCP)
This method is likely overkill, you have your C++ program act as TCP server and your python program connects to it and sends it the orders as they come in. You should be aware that programming this option would be significantly harder to the previous options, however it provides an instant response that the others don't.
Easy to implement BaseHttpServer on python, use pipe to communicate with c++ process and proxy_pass clients`s requests via web server.

how can i test sharepoint custom web service

hi all
i coded a custom web service for sharepoint in a remote machine and will deploy it later to the host machine
but how programs do i need to install to my computer to test that web service
Use a tool such as
Web Service Studio
(All open source)
You'll probably need a test application to sit on the same system as the web service.
It will locally fire the webservice and some of the test fixtures will only monitor what it returns.
The rest of the fixtures should examine what the webservice actually interacts with on the server side.
ie: If you have a webservice that accepts a command then starts a Workflow, you would:
a) Ensure that the correct response is given by the webservice when invalid input is given
b) Ensure on the server side that the correct workflow is instigated and started with the correct initialisation data.
You would probably need many, many test cases depending on what your webservice actually does.