Roadmap for 24x7

24x7 is going to become a critical part of a new service I am looking to develop and I would like to ensure that the product has a future. Can you confirm that your company plans to continue to develop the 24x7 product and also would it be possible to see a roadmap of future developments?

Thanks.

To the best of my knowledge we have no plans to abandon 24x7.

Among publicly stated enhancements in future versions are:
-- fully merge Windows-only and MP versions into one single product
-- adding multi-server push capabilities 1 job pushed concurrently to multiple servers
-- implementing more web automation methods for file downloading/uploading/page content manipulation,/etc…
-- improving JavaScript engine and essentially providing JavaScript supporting all methods that are currently available in JAL but covering multiple platforms, not just Windows.
-- improving job dependencies editor and job workflow
-- improving job output capturing methods and simplifying job output monitoring and analysis (adding graphical interface as it seems that many people have difficulties with adding simple output redirection > and >> to job command lines)

That all looks like great stuff and gives me a good feel for the future and therefore to make 24x7 vital in my project design. Thanks.

	Quote:
	-- fully merge Windows-only and MP versions into one single product

I do not feel very well with this statement. When trying to run our Environment with the MP Version, I encountered the following:
- A MP Scheduler 4.2.278 is not able to run a job on a Remote agent that consists of a Windows-only 3.5.2 Edition, as I could read here in the forums this is because of the incompatible License Keys.
- We have a Layout of one Server that runs the Scheduler and 3 Windows XP Workstations where the Remote Agents run. On the Windows XP Workstations there is a user logged on with Network drives mapped to drive letters - this is needed by the Applications that is to be run remotely. We can start the application from the Windows Agent just fine. Trying the same from the MP Agent results in a "The System cannot find the path specified" - I suppose, this results from the technique to start the App as "Run As" that is used by the MP Agent.

So I have not a good feeling when Windows-only Version and MP Version shall be merged into one single product as I suppose that the behavior of the resulting agent will be the behaviour of the MP Agent, isn't it?

Kind Regards
Christian

Hi,

	Quote:
	I do not feel very well with this statement. When trying to run our Environment with the MP Version, I encountered the following: - A MP Scheduler 4.2.278 is not able to run a job on a Remote agent that consists of a Windows-only 3.5.2 Edition, as I could read here in the forums this is because of the incompatible License Keys.

This is a non-technical issue. You need a site license to do that. You don't need a site license if you use Windows-to-Windows version communication or MP-to-MP version communication. Comparing MP to Windows version, MP version provides more sophisticated capabilities for remote automation and remote job running. I also want to mention its ability to encrypt its network communications. I highly recommended using MP scheduler with MP agents, rather then trying to make MP scheduler to talk to Windows version agents.

Quote:

- We have a Layout of one Server that runs the Scheduler and 3 Windows XP Workstations where the Remote Agents run. On the Windows XP Workstations there is a user logged on with Network drives mapped to drive letters - this is needed by the Applications that is to be run remotely. We can start the application from the Windows Agent just fine. Trying the same from the MP Agent results in a "The System cannot find the path specified" - I suppose, this results from the technique to start the App as "Run As" that is used by the MP Agent.

Using drive mapping is only ok if you don't run the agent as a service (doesn't matter Windows or MP agent)
As for the "cannot find the path" please let us know the command line you are trying to run. I'm quote sure with a little tweaking that command could be made to run just fine with MP agent.

	Quote:
	So I have not a good feeling when Windows-only Version and MP Version shall be merged into one single product as I suppose that the behavior of the resulting agent will be the behaviour of the MP Agent, isn't it?

There are some minor differences, but they are really very minor. I think you have stumbled against some particular case requiring slightly different approach and have made a conclusion based on that case.