JobServer可以作为创建和加强您公司的业务流程以及内/外部作业处理的基础。JobServer提供了丰富的特性及高度可扩展的环境，它可将计算最密集的数据库ETL处理中的一切事务调度和运行到关键的业务处理，Web服务调用和单调的邮件通知中。
JobServer can be the foundation for building and consolidating your company's business processes and internal/external job processing. JobServer provides a feature rich and highly scalable environment for scheduling and running everything from your most compute intensive database ETL processing, to critical business number crunching, to web services calls, to the mundane email notifications.
强大的工具集
JobServer包含大量丰富的GUI工具集来管理作业和环境。您可以高精度高细节地设计，调度，运行以及跟踪作业。通过使用JobServer您能知道作业是怎样运行的，它正在运行什么内容以及它何时在运行，您也能知道某个作业最后一次是被谁修改的，谁最后关闭了服务器等等……如果一个作业抛出错误或警告，您可通过邮件得到通知或者通过任何一组作业搜寻那样的情况（极好的可用报告特性）。当作业运行时，您能知道具体是什么被发送给了客户，知道当作业运行时输入是什么以及该作业产生了什么输出。JobServer对一个作业从其创建开始到每次运行的整个过程都了如指掌。
调度引擎
JobServer调度引擎并没有局限于一种调度规则。实际上，任何您能想到的重复或一次性的调度模式都可以通过JobServer调度引擎展示出来。下面举例说明了一些该引擎所支持的调度规则：
从2003年1月1日上午9点开始，每15分钟进行一次，只能在上午10点和下午7点半之间进行，结束时间是2004年3月3日下午5点
从2003年1月1日上午9点开始，在每个月的最后一个，第一个及第二个星期一和最后一个星期五进行
从2003年7月7日开始，在每个星期的星期一和星期三进行，2003年7月30日的星期三除外
多个一次性的日期可从任何调度安排中进行添加或移除。例如，这是一个简单的方式用来添加或移除公司假期。
日内的多个时间范围可被移除（例如，将早上1点至早上4点移除）
如果调度时间因为当机而丢失，则过去的调度时间可跳到之后或者当调度时间被移至到未来的某个日期时进行一次一个地执行。
在执行完一定数量的调度之后作业可被设置为停止运行（例如在运行了55次之后停止）。
过期窗口意味着一个作业需要从它的调度时间开始运行在一个特定的时间窗口中，否则它将过期;（当发生这种情况时管理员会被提醒）。
当作业失败时可设置多层邮件提醒。可设置为JobServer层，分区层，作业组层和/或个人作业层。
JobServer可根据适用的硬件调整其规模。它的设计利用了多处理器及多核系统的优势。JobServer采用了先进的超前缓存模式以确保在准备运行作业时没有时间浪费。它采用了先进的多线程扫描设计能有效地检测哪个作业准备就绪并迅速调度它们运行。调度引擎和相应的作业处理单元可被分割到任何数目的分区中。分区允许更高程度的并发并且对于那些包含了大量数目作业的设施来说是至关重要的，同时调度的及时性也是至关重要的。一个分区也可以被定义用于限制并发运行的作业数量从而避免资源超负荷。无论您是管理少量的作业还是成千上万的作业，JobServer都是您的不二选择。
一些先进的特性包括：
作业依赖性调度
作业依赖性规则可用于控制相互关联的作业。例如，您有一个作业A每天必须在一组其它的作业被允许开始之前运行并完成。在这种情况下，为满足依赖性，当作业A未完成时，组内的其它作业将不会被调度。
作业时间版本控制
想象您有一个作业通过电子邮件被发送给了客户。下个月您需要更改邮件地址，作业时间版本控制允许您更改一个作业的属性并且让它们在今后的时间点上生效。您可以为一个作业设置任意数量的后期版本。
分区和分组
将JobServer环境分为多个计算分区用于管理和控制处理器，数据库及其它资源利用。进一步将作业分组并限制用户的权利，使得它们只能访问作业组和分区内的资源。
详细的作业运行计量及跟踪
JobServer不仅仅是对作业何时运行及它们如何完成其处理过程进行一般地报告，它还清楚地知道作业运行的输入及作业运行时产生的输出。JobServer可跟踪一个作业每次运行时准确的输入和输出。这使得用户和管理员可以查询历史记录，了解作业运行的准确时间及其配置信息，并根据这些详细的证据知道作业中哪些已经完成，哪些还未完成。
开发者API
开发者API的目的是使公司可以按照他们的设想以模块化和可重用的方式创建他们自己的作业。许多特性是可选的，因此您可以选择您希望采用的特性层和可重用层。为创建一个将要运行在JobServer中的作业，所有需要做的便是实现一个接口并将所开发的Java软件放到合适的JAR文件中。作业可以只是一行代码，也可以是数千行代码。
支持开源
SOAFaces API是JobServer用来定义一个作业做什么以及它在服务器中如何执行的创新基础。该API是在一个开源机构上开发的，它允许开发者参与并推动创新，它甚至没有锁定供应商。在SOAFaces中还有一个子项目叫做BeanSoup。BeanSoup是SOAFaces中可重用组件的一个集合，它是在一个开发者社区中开发完成的。
基于构件的软件开发在这里！
JobServer通过允许开发者创建和构造叫做SOAFaces的软件构件实现了推动创新。在JobServer中调度和执行的每个作业是由一个或多个SOAFaces组成的。一个SOAFaces构件（又名tasklet）可以只是简单的一行代码或者是复杂的成千上万行代码或者更多。开发者可选择性地开发这些tasklets，他们可以接受输入并将输出发送至其它的tasklets。这些操作全部可以通过一个简单的POJO（简单的Java对象）API来实现，因此没有供应商锁定，开发者也无须学习复杂的API。所有繁重的任务都是由JobServer容器来完成的。举一个例子，所有的日志都是通过标准的Java日志API实现的，而JobServer容器则管理着日志输出。GUI工具用于搜索和查看日志。如果一个tasklet希望将其输出展示给其它的tasklets，它可以通过定义一个简单的JavaBean来实现，并且它还能选择性地定义其它的tasklets中哪些可作为其输入传入（使用一个输出JavaBean）。更重要的是，用户可以使用JavaBean GUI定制器直观地编辑JavaBean上的这些输入属性。
Powerful Tools
JobServer comes with a rich set of GUI tools by which to manage your jobs and environment. You can design, schedule, run, and track your jobs with a high degree of precision and detail. Know how, what, and when a job ran. Know who last modified a job's schedule, who last shutdown the server ...etc. If a job throws errors or warnings get notified by email or quickly search for such conditions across any set of jobs (great reporting features available). When a job runs, know exactly what was sent to the customer. Know what inputs the job used when it ran and what outputs it generated. JobServer knows everything about a job from the time it is created all the way through each and every run.
Scheduling Engine
The JobServer Scheduling Engine leaves no scheduling rule out of your reach. Virtually, any repeating or one-off scheduling pattern that you can imagine can be represented using the JobServer Scheduling Engine. As an example, here is a sample of scheduling rules that are supported:
- Every 15 minutes starting on 1/1/2003 09:00AM and only between 10:00AM and 7:30PM and ending on 3/3/2004 5:00PM
- Every other month starting on 1/1/2003 09:00AM and on the last, first and second Monday and last Friday of the Month
- Every other Week on Monday and Wednesday starting on 7/7/2003 except for Wednesday of 7/30/2003
- Multiple one-off dates can be added or excluded to any schedule. For example, this is a convenient way to include or exclude company holidays.
- Multiple intra-day time ranges can be excluded (e.g. exclude 1:00am to 4:00am)
- If schedule times are missed due to down time, past scheduling times can be skipped ahead to the future or can be executed one at a time until the schedule has moved to a date in the future.
- Jobs can be set to stop running after a certain number of scheduled executions (e.g. stop after the job has run 55 times).
- Expire window requires a job run within a certain time window from its scheduled time, otherwise, it will "expire" (administrators can be alerted when this happens).
- Multiple levels of email alert can be setup when jobs fail. This can be setup at the entire JobServer level, Partition level, Job Group level, and/or individual job level.
JobServer can scale with the hardware that is available to it. It is designed to take advantage of multi-CPU and multi-core systems. The JobServer uses an advanced look-ahead caching scheme to make sure that no time is wasted when preparing to run a Job. It employs an advanced multi-thread scanning design to efficiently detect what Jobs are ready to run and quickly prepare them for running. The Scheduling Engine and corresponding job processing unit can be segmented into any number of Partitions. Partitions allow for higher degrees of concurrency and are vital for installations that have a large number of jobs and where scheduler promptness is critical. A Partition can also be defined to limit the number of concurrently running Jobs to avoid resource overload. Whether you are manging a handful of jobs or tens of thousands of jobs, JobServer is up the task.
Some of the advanced features include:
Job Dependency Scheduling
Job dependency rules can be defined to control when jobs can run relative to each other. For example, say you have job A that must run and complete each day before a group of other jobs may be allowed to start. In this case, the jobs in the group will not be scheduled so long as job A has not completed and satisfied the dependency.
Job Time Versioning
Imagine you have a job that sends an email to a customer. Now next month you know that you will need to change this email address. Job Time Versioning allows you to change a job's properties and have them take effect at a future time. You may set an arbitrary number of future versions for a job.
Partitions and Groupings
Segment your JobServer environment into multiple computing Partitions to manage and control CPU, database, and other resource utilization. Further organize jobs into Groups and then restrict users rights to only the Job Groups and Partitions you want them to have access to.
Detailed Job Run Accountability and Tracking
JobServer goes beyond just general reporting of when jobs run and how they completed their processing. Know exactly what inputs the job used when it was run and exactly what outputs it generated as it ran. JobServer can track the exact inputs/outputs used by a job for each and every run. This give the user and administrator the ability to go back into history, at the exact time the job was run, and know how it was configured. This allows you to give customers and users detailed proof of what was or wasn't done to the job.
Developer API
The goal of the developer API is to allow companies to build their own jobs in a modular and reusable fashion as they so desire. Many of the features are optional, so you may choose the level of functionality and reusability that you wish to employ. To create a job that will run in JobServer, all it takes is implementing one interface and putting the developed Java software into an appropriate JAR file. The job can be one line of code or thousands of lines of code.
Support for Open Source
he SOAFaces API is an innovative foundation that JobServer uses to define what a job does and how it executes within a server. The API is developed on an open source foundation allowing developers to get involved and drive innovation even further, and without vendor lock in. There are also a sub project called BeanSoup that builds on the SOAFaces. BeanSoup is a collection of reusable SOAFaces components implemented and contributed by a community of developers.
Component Software Development is Here!
JobServer is driving innovation by allowing developers to build and compose component software called SOAFaces. Every job that is scheduled and executed within the JobServer environment is composed of one or more SOAFaces. A SOAFaces component (aka tasklet) can be as simple as a single line of code or as complex as ten thousand or more. Developers have the option of developing these tasklets in such as way that they can accept input and send output to other tasklets. This is all done using a simple POJO (plain old Java objects) API, so that there is no vendor lock in or complex API for developers to learn. All the heavy lifting is done by the JobServer Container. As an example, all logging is done using the standard Java Logging API where the JobServer Container manages the log output. GUI tools are provided to search and view the logs. If a tasklet wishes to expose its outputs to other tasklets, it can do so by defining a simple JavaBean and it can optionally define what inputs can be passed to it from other tasklets (using an output JavaBean). What's more, is that users can also visually edit these input properties on the JavaBean using JavaBean GUI Customizers.
彩票走势图 
相关产品
授权相关问题
微信
在线咨询
渝公网安备
50010702500608号
客服热线