topic Re: SAS WIP scheduling services in Administration and Deployment

SAS WIP scheduling services

SASWayne — Mon, 26 Oct 2020 14:16:48 GMT

I'm trying to understand what is a Web Infrastructure Platform scheduling service that runs on middle tier.

is it something that is used to by webapps to schedule flows?

How it works in the background?

What is its purpose?

etc.

I'm having hard luck in finding its documentation, could someone point me to the documentation or explain in a detailed way about WIP scheduling services in my post?

Re: SAS WIP scheduling services

gwootton — Mon, 26 Oct 2020 15:57:52 GMT

The purpose of WIP Scheduling Services is to make scheduling available generally through the middle tier so solutions can schedule their jobs without needing to have information on how to schedule to any given scheduler themselves (i.e. a scheduling API). The documentation on scheduling in a particular solution would be in that solution's documentation, behind the scenes they would make use of this service.

Re: SAS WIP scheduling services

SASWayne — Mon, 26 Oct 2020 16:13:05 GMT

Thank you very much! I just have some more questions below.

How do we administer WIP scheduling services like start/stop?

is it tied with any mid tier component like webapp/webserver, locator etc.?

Does the solution be able to choose which scheduler (PPM, in-process, etc.)
be used for scheduling?

Does WIP scheduling service need any configuration when the environment is
setup initially?

is there a log/configuration folder available for WIP scheduling services
incase if any troubleshooting is needed?

How does the WIP scheduling service submit schedules to PPM (I mean the
internal process happens within SAS after it receives schedule flow
requests from a solution)?

Thanks in advance!!!

Re: SAS WIP scheduling services

gwootton — Mon, 26 Oct 2020 17:43:27 GMT

1. WIP Scheduling Services runs on SASServer1, so starting and stopping it would be done there by stopping/starting SASServer1.
2. Yes, it is a web application on SASServer1.
3. If the solution opts to make this an option, yes.
4. No, it does not need to be separately configured.
5. It is a web application so SASServer1_1's catalina.out, server.log and the WIPServices log in Lev1/Web/Logs/SASServer1_1 would be the associated log files.
6. Process Manager accepts job submissions through a TCP connection to it's port (1966 by default). The WIP Scheduling Service submits jobs through a connection to Process Manager on that port.

Re: SAS WIP scheduling services

SASWayne — Tue, 27 Oct 2020 17:33:18 GMT

Thank you very much @gwootton!

Re: SAS WIP scheduling services

SASWayne — Mon, 02 Nov 2020 16:26:15 GMT

@gwootton
SAS WIP SOAP service is as same as SAS WIP scheduling services? or a different one?
If it is different, does it also run on SASServer1_1?
does it need to be started/stopped separately?
does it require any separate configuration?

Re: SAS WIP scheduling services

gwootton — Mon, 02 Nov 2020 17:21:38 GMT

The SOAP service is different from scheduling services, but both are part of the Web Infrastructure Platform (WIP) that runs on SASServer1_1. SASWIPSoapServices is it's own web application.

It is still started/stopped by starting/stopping SASServer1 and does not require configuration outside of the normal deployment process.