The same folder ( /PATH/TO/RAPIDMINER/HOME) is used to mount licenses for the Job Agent. The examples use the folders /PATH/TO/PGSQL/HOME for persistent PostgreSQL data and /PATH/TO/RAPIDMINER/HOME for persistent rapidminer-home data.JOBAGENT_AUTH_SECRET and JOBSERVICE_AUTH_SECRET values are Base64 encoded strings.The value of the required JOBAGENT_AUTH_SECRET, JOBAGENT_QUEUE_ACTIVEMQ_USERNAME and JOBAGENT_QUEUE_ACTIVEMQ_PASSWORD parameters are printed out to the console during the RapidMiner Server container startup. For production use, it is highly recommended to define queues and have external Job Agent containers connect to them. A bundled Job Agent is included in the image for testing purposes, but its data persistence is not solved.The default login credentials are admin/changeit.You can connect to it on or any other network interface. RapidMiner Server listens on port 8080, as described in the previous examples.On Windows hosts, please make sure that the Docker Engine is configured to run with enough memory. RapidMiner Server requires at least 8GB of memory. The configuration can be tuned via files stored in /configuration.Licences can be installed in /resources/licenses.Extensions can be installed by adding them to the folder /resources/extensions.After the first execution (with a mounted empty volume), the following data can be edited: This volume will contain all the configuration files, extensions, licenses, logs and repository data. If the volume contains data from any previous executions, then the server will be started with that data.If the mounted volume is empty, then a default configuration and data content will be propagated to it for use by RapidMiner Server.To make this data persistent, make sure to start the container with a volume mounted on the mount point /persistent-rapidminer-home, as indicated by the -v option to docker run in the examples below, or the volumes option in docker-compose.yml. The RapidMiner home directory stores all the data and configuration connected with the RapidMiner Server image. The server can be configured, plugins can be installed and afterwards the RapidMiner Server process can be started manually. INTERACTIVE_MODE: setting this variable to "1" will start an interactive bash shell without starting the RapidMiner Server process.JOBAGENT_QUEUE_ACTIVEMQ_USERNAME, JOBAGENT_QUEUE_ACTIVEMQ_PASSWORD, JOBAGENT_AUTH_SECRET: set these variables to configure the bundled Job Agents' connection credentials.BROKER_ACTIVEMQ_USERNAME, BROKER_ACTIVEMQ_PASSWORD and JOBSERVICE_AUTH_SECRET: set these variables to define the required authentication secret and ActiveMQ credentials that should be used in the Job Agents.If the provided database is empty (there is no table), it will be initialized with an initial RapidMiner Server database. DBHOST, DBUSER, DBPASS, DBSCHEMA: set these variables to configure RapidMiner Server to use an external PostgreSQL database.BUNDLED_JOB_AGENT: set this to "1" in order to start the bundled Job Agent.The persistence of the data using an embedded database server is not solved. EMBEDDED_DATABASE: set this to "1" in order to start the embedded PostgreSQL database server in the container.For production, use an external database to ensure data persistence.For quick deployments, there is an embedded database, but it is not recommended for production.The image provides two different database connection methods: This is a fully functional RapidMiner Server image.įor available versions, please see the tags: RapidMiner Server ( rapidminer/rapidminer-server:latest)įor Docker images, see Docker Hub.The documentation below describes the following Docker image:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |