
Geir Otto Olsen (THInc Consulting AS) asked a question.
12.8
I have used older version of Pro2 - 5.5, and found it easy to understand. When entering into v.6.5, that is not the issue. The new UX is difficult to get a hang of. Take the reporting, you go one place to find the menu, you run it, and you have to find the result a different place. Ok, it is the web way, but it is still not easy to get a hang of.
Anyway, so I need to understand how it works.
question 1:
To get the jobhandler (the one that checking for pending jobs), do I need to start the bprepl/scritps/jobrunners.bat ? It seems like that, so I added it to a service that is handling it, but do I need to do it like that ?
question 2:
In v.5.5 I needed to run replbatch.bat or replbatch<>.bat, or like I did, started each thread by services, and that worked swell, as well. I get a bit confused when looking at the documentation:
I assume that the jobrunner is the heart of this, and that the jobrunner process is checking the scheduler for jobs, finds and execute them. Take the Replication Thread, in earlier version 5.5 I needed to start the threads, but no I seems like I can add them to this scheduler, and something magical will happen. Is it the jobrunner that does that work?
I tested by adding a replication thread and said it should have started for 2 days ago, and run each 2 minute. I never saw anything happened in the Total threads view. I started to of them the old way, by adding two services that ran each thread, and then I saw them as active threads:
But is that the way to do it?
When it comes to the documentation, I find it difficult to find what I am looking for. Probably because my English is not that good, but what to say...
question 5:
I am trying to find out how to migrate from v5.5, and as far as I understand, I need to do a full reload, just forgetting the old SQL replication databases. Make them new, and push everything back into them. Is that correct?
//frustrated Pro2 dummy
Hi @Geir Otto Olsen (THInc Consulting AS),
Yes, you need to start the job runner first. Here are the steps https://docs.progress.com/bundle/openedge-pro2/page/Use-the-job-runner.html
Then various jobs like Replication thread run, CDC thread run etc will work, you can start them from the Schedule Jobs screen https://docs.progress.com/bundle/openedge-pro2/page/How-to-schedule-jobs-in-Pro2.html
I hope this will help!
Thanks,
Talha
I got that, so jobrunner needs to run. I have started that, and it is running as a windows service.
I then see that the various jobs that can be run and one is for threads. I tested that, and I can see that it start, and stops as I assume it would do. Since it seems like it is the jobrunner that is responsible for running the jobs, I also assume that it would run one thread at time? In my case, I create two jobs that is running replication thread 1 and 2, I have two databases, and database1 is handle by thread1 and the other is handled by thread2.
I started one using replbatch, and one using jobscheduler. The result regarding total threads:
@Geir Otto Olsen (THInc Consulting AS), Use the Thread control box on the dashboard to update thread logging-level & disposition.
https://docs.progress.com/bundle/openedge-pro2-web-ui/page/Thread-control.html
Use the filter button on the top left corner of the dashboard to set the refresh settings for Watch boxes, Dashboard Graphs, Thread Control, and Thread Sleep.
https://docs.progress.com/bundle/openedge-pro2-web-ui/page/Dashboard-settings.html
Thanks Talha ! you made my day :-)
Happy to help!
Thanks, did you see my problem regarding sql and width problem ? do you know anything about that? :-)