FAQ - Revision history

Craig: /* What technologies does Obsidian use? */

2023-12-26T02:02:08Z

What technologies does Obsidian use?

← Older revision		Revision as of 02:02, 26 December 2023
Line 22:		Line 22:

	== What technologies does Obsidian use? ==		== What technologies does Obsidian use? ==
	Obsidian is built on Java ~~1.7~~, and will run on newer versions as well. The admin web application requires a servlet container, such as Tomcat or Jetty. Obsidian also requires a database such as MySQL or Oracle, where scheduling data is stored. Obsidian has a small set of [[Advanced_Configuration#Dependent_Libraries\|library dependencies]] (.jar files), selected to avoid conflicts with our users' own libraries. See [[Getting Started]] for details on which versions of servlet containers and database platforms are supported.		Obsidian is currently built on Java 11, and will run on newer versions as well. The admin web application requires a servlet container, such as Tomcat or Jetty. Obsidian also requires a database such as MySQL or Oracle, where scheduling data is stored. Obsidian has a small set of [[Advanced_Configuration#Dependent_Libraries\|library dependencies]] (.jar files), selected to avoid conflicts with our users' own libraries. See [[Getting Started]] for details on which versions of servlet containers and database platforms are supported.

	== Why should I use Obsidian? ==		== Why should I use Obsidian? ==

Craig at 19:45, 7 June 2023

2023-06-07T19:45:45Z

← Older revision		Revision as of 19:45, 7 June 2023
Line 61:		Line 61:
	== Why isn't my job showing up? ==		== Why isn't my job showing up? ==

	Out of the box, Obsidian will display any previously scheduled jobs and Obsidian's bundled jobs. You can type in your class name as described in [[Admin_Jobs#~~Job_Nickname_and_Class~~\|Admin Jobs]].		Out of the box, Obsidian will display any previously scheduled jobs and Obsidian's bundled jobs. You can type in your class name as described in [[Admin_Jobs#Nickname.2C_Class_and_Folder\|Admin Jobs]].

	As of '''Obsidian 2.2.1''', you can take advantage of our [[Spring_Integration\|Spring Integration]]. Jobs that have been wired into your <code>ApplicationContext</code> will be available in the list.		As of '''Obsidian 2.2.1''', you can take advantage of our [[Spring_Integration\|Spring Integration]]. Jobs that have been wired into your <code>ApplicationContext</code> will be available in the list.

Craig at 19:43, 7 June 2023

2023-06-07T19:43:31Z

Craig at 14:46, 23 May 2023

2023-05-23T14:46:08Z

← Older revision		Revision as of 14:46, 23 May 2023
Line 9:		Line 9:

	== How do I set up Obsidian? ==		== How do I set up Obsidian? ==
	Check our [[Getting Started]] guide, or email us at our [https://web.obsidianscheduler.com/support support address].		Check our [[Getting Started]] guide, or email us at our [https://web.obsidianscheduler.com/support/ support address].

	== Is it free? ==		== Is it free? ==

Craig: /* How do I get my job application code running in the Obsidian WAR or standalone scheduler? */

2023-05-23T14:45:29Z

How do I get my job application code running in the Obsidian WAR or standalone scheduler?

← Older revision		Revision as of 14:45, 23 May 2023
Line 49:		Line 49:
	If you are running a Obsidian as a standalone scheduler, embedded in your application, or in the WAR with scheduling enabled, you need to ensure your application JARs are on the classpath. In the WAR, this means adding your JAR files to the <code>WEB-INF/lib</code> directory. If you are embedding Obsidian, it will already have access to the application's classpath. If running as a standalone scheduler, you will have to add your application JARs to the <code>/lib</code> directory. Note that you must include any JARs that contain your job classes, as well as those that contain dependent code.		If you are running a Obsidian as a standalone scheduler, embedded in your application, or in the WAR with scheduling enabled, you need to ensure your application JARs are on the classpath. In the WAR, this means adding your JAR files to the <code>WEB-INF/lib</code> directory. If you are embedding Obsidian, it will already have access to the application's classpath. If running as a standalone scheduler, you will have to add your application JARs to the <code>/lib</code> directory. Note that you must include any JARs that contain your job classes, as well as those that contain dependent code.

	If you are running a standalone web application that does not have a scheduler running, you do not have to update its classpath with your compiled jobs, unless you are running a version older than 2.6, but there are steps you need to take which are outlined in [[Implementing_Jobs#Classpath_for_Building\|Classpath for Building ~~and Deploying~~]].		If you are running a standalone web application that does not have a scheduler running, you do not have to update its classpath with your compiled jobs, unless you are running a version older than 2.6, but there are steps you need to take which are outlined in [[Implementing_Jobs#Classpath_for_Building\|Classpath for Building]].

	== How do scripting jobs work? ==		== How do scripting jobs work? ==

Craig at 14:44, 23 May 2023

2023-05-23T14:44:37Z

← Older revision		Revision as of 14:44, 23 May 2023
Line 49:		Line 49:
	If you are running a Obsidian as a standalone scheduler, embedded in your application, or in the WAR with scheduling enabled, you need to ensure your application JARs are on the classpath. In the WAR, this means adding your JAR files to the <code>WEB-INF/lib</code> directory. If you are embedding Obsidian, it will already have access to the application's classpath. If running as a standalone scheduler, you will have to add your application JARs to the <code>/lib</code> directory. Note that you must include any JARs that contain your job classes, as well as those that contain dependent code.		If you are running a Obsidian as a standalone scheduler, embedded in your application, or in the WAR with scheduling enabled, you need to ensure your application JARs are on the classpath. In the WAR, this means adding your JAR files to the <code>WEB-INF/lib</code> directory. If you are embedding Obsidian, it will already have access to the application's classpath. If running as a standalone scheduler, you will have to add your application JARs to the <code>/lib</code> directory. Note that you must include any JARs that contain your job classes, as well as those that contain dependent code.

	If you are running a standalone web application that does not have a scheduler running, you do not have to update its classpath with your compiled jobs, unless you are running a version older than 2.6, but there are steps you need to take which are outlined in [[Implementing_Jobs#~~Classpath_for_Building_and_Deploying~~\|Classpath for Building and Deploying]].		If you are running a standalone web application that does not have a scheduler running, you do not have to update its classpath with your compiled jobs, unless you are running a version older than 2.6, but there are steps you need to take which are outlined in [[Implementing_Jobs#Classpath_for_Building\|Classpath for Building and Deploying]].

	== How do scripting jobs work? ==		== How do scripting jobs work? ==

Craig: /* How can I deploy job changes without redeploying or restarting Tomcat? */

2023-05-17T15:48:47Z

How can I deploy job changes without redeploying or restarting Tomcat?

← Older revision		Revision as of 15:48, 17 May 2023
Line 76:		Line 76:
	Apart from using the [[Job Forking]] support noted above, if you want truly dynamic job changes that even support configuration additions/removals, the best approach we can offer for this is to use our embedded [[Scripting_Jobs\|Scripting]] support.		Apart from using the [[Job Forking]] support noted above, if you want truly dynamic job changes that even support configuration additions/removals, the best approach we can offer for this is to use our embedded [[Scripting_Jobs\|Scripting]] support.

	You can either use something like the included <code>GroovyJob</code>, or write your own job that executes a job script on the file system. The latter approach lets you just replace script files on demand. If you use this approach, you can define a Java job which accepts a defined script name parameter, which you can then execute using ~~Groovy's~~ [~~http~~://groovy~~.codehaus~~.org/~~Embedding+~~Groovy ~~embedding support~~], or one of our other supported scripting languages.		You can either use something like the included <code>GroovyJob</code>, or write your own job that executes a job script on the file system. The latter approach lets you just replace script files on demand. If you use this approach, you can define a Java job which accepts a defined script name parameter, which you can then execute using [https://docs.groovy-lang.org/latest/html/documentation/guide-integrating.html Groovy], or one of our other supported scripting languages.

	== What level of scheduling precision does Obsidian support? ==		== What level of scheduling precision does Obsidian support? ==

Craig at 15:41, 17 May 2023

2023-05-17T15:41:16Z

← Older revision		Revision as of 15:41, 17 May 2023
Line 16:		Line 16:
	For additional licenses, including clustering nodes, the cost starts at $649 CAD each. For example, if you want to run a 2-node cluster, after the first year you would need to purchase a single $649 license. This license gives you access to free support and all future versions of the product.		For additional licenses, including clustering nodes, the cost starts at $649 CAD each. For example, if you want to run a 2-node cluster, after the first year you would need to purchase a single $649 license. This license gives you access to free support and all future versions of the product.

	Obsidian also provides other licensing options which can be found on our [https://web.obsidianscheduler.com/~~licensing~~ main site].		Obsidian also provides other licensing options which can be found on our [https://web.obsidianscheduler.com/pricing/ main site].

	== Is it open source? ==		== Is it open source? ==

Craig at 03:09, 4 May 2023

2023-05-04T03:09:48Z

← Older revision		Revision as of 03:09, 4 May 2023
Line 9:		Line 9:

	== How do I set up Obsidian? ==		== How do I set up Obsidian? ==
	Check our [[Getting Started]] guide, or email us at our [~~http~~://obsidianscheduler.com/support support address].		Check our [[Getting Started]] guide, or email us at our [https://web.obsidianscheduler.com/support support address].

	== Is it free? ==		== Is it free? ==

Craig: /* Is it free? */

2021-08-05T03:50:16Z

Is it free?

← Older revision		Revision as of 03:50, 5 August 2021
Line 12:		Line 12:

	== Is it free? ==		== Is it free? ==
	We grant free single-node licenses which you can use forever free of charge ([~~http~~://obsidianscheduler.com/download/ download here]). In addition, you get a second node that you can use for one year free of charge to allow you to evaluate Obsidian clustering.		We grant free single-node licenses which you can use forever free of charge ([https://web.obsidianscheduler.com/download/ download here]). In addition, you get a second node that you can use for one year free of charge to allow you to evaluate Obsidian clustering.

	For additional licenses, including clustering nodes, the cost is $~~499~~ CAD each. For example, if you want to run a 2-node cluster, after the first year you would need to purchase a single $~~499~~ license. This license gives you access to free support and all future versions of the product.		For additional licenses, including clustering nodes, the cost starts at $649 CAD each. For example, if you want to run a 2-node cluster, after the first year you would need to purchase a single $649 license. This license gives you access to free support and all future versions of the product.

	Obsidian also provides other licensing options which can be found on our [https://obsidianscheduler.com/licensing main site].		Obsidian also provides other licensing options which can be found on our [https://web.obsidianscheduler.com/licensing main site].

	== Is it open source? ==		== Is it open source? ==

← Older revision		Revision as of 19:43, 7 June 2023
Line 101:		Line 101:
	Here are definitions of some acronyms commonly used in Obsidian's documentation.		Here are definitions of some acronyms commonly used in Obsidian's documentation.

	* DB/DBMS - [~~http~~://en.wikipedia.org/wiki/Database Database Management System]: A software application which provides storage and querying of a collection of data.		* DB/DBMS - [https://en.wikipedia.org/wiki/Database Database Management System]: A software application which provides storage and querying of a collection of data.
	* SQL [~~http~~://en.wikipedia.org/wiki/SQL Structured Query Language]: A language used to query databases.		* SQL [https://en.wikipedia.org/wiki/SQL Structured Query Language]: A language used to query databases.
	* API - [~~http~~://en.wikipedia.org/wiki/Application_programming_interface Application Programming Interface]: A set of code routines, protocols or tools used to build software applications.		* API - [https://en.wikipedia.org/wiki/Application_programming_interface Application Programming Interface]: A set of code routines, protocols or tools used to build software applications.
	* REST [~~http~~://en.wikipedia.org/wiki/Representational_state_transfer Representational State Transfer]: A style of building a web-based API using common practices which is typically available over HTTP.		* REST [https://en.wikipedia.org/wiki/Representational_state_transfer Representational State Transfer]: A style of building a web-based API using common practices which is typically available over HTTP.
	* HTTP [~~http~~://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol Hypertext Transfer Protocol]: The communication protocol used for the world wide web and most REST APIs.		* HTTP [https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol Hypertext Transfer Protocol]: The communication protocol used for the world wide web and most REST APIs.
	* JRE - [~~http~~://en.wikipedia.org/wiki/~~Java_virtual_machine~~#~~Java_Runtime_Environment_from_Oracle~~ Java Runtime Environment]: Java applications run through a JRE.		* JRE - [https://en.wikipedia.org/wiki/Java_(software_platform)#Java_Runtime_Environment Java Runtime Environment]: Java applications run through a JRE.
	* JDK - [~~http~~://en.wikipedia.org/wiki/Java_Development_Kit Java Development Kit ]: A set of Java tools which provide development and compilation support. Some applications require a JDK to run.		* JDK - [https://en.wikipedia.org/wiki/Java_Development_Kit Java Development Kit ]: A set of Java tools which provide development and compilation support. Some applications require a JDK to run.
	* JAR - [~~http~~://en.wikipedia.org/wiki/JAR_(file_format) Java Archive File ]: The standard packaging unit for Java code libraries.		* JAR - [https://en.wikipedia.org/wiki/JAR_(file_format) Java Archive File ]: The standard packaging unit for Java code libraries.
	* WAR - [~~http~~://en.wikipedia.org/wiki/WAR_(file_format) Web Application Archive ]: A way to package Java web applications which can be deployed in a standardized way.		* WAR - [https://en.wikipedia.org/wiki/WAR_(file_format) Web Application Archive ]: A way to package Java web applications which can be deployed in a standardized way.
	* JDBC - [~~http~~://en.wikipedia.org/wiki/Java_Database_Connectivity Java Database Connectivity]: An API which provides database access to Java applications.		* JDBC - [https://en.wikipedia.org/wiki/Java_Database_Connectivity Java Database Connectivity]: An API which provides database access to Java applications.

	== What is the default username and password? ==		== What is the default username and password? ==

	Each Obsidian installation using native authentication (the default) starts with a single default user named '''admin''' with password '''changeme'''. You should change this after your first login. See [[User Management]] for how to change a user's password.		Each Obsidian installation using native authentication (the default) starts with a single default user named '''admin''' with password '''changeme'''. You should change this after your first login. See [[User Management]] for how to change a user's password.