You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/03/01 02:39:59 UTC
[GitHub] apiri commented on a change in pull request #492: MINIFICPP-746:
carve and improve documentation
apiri commented on a change in pull request #492: MINIFICPP-746: carve and improve documentation
URL: https://github.com/apache/nifi-minifi-cpp/pull/492#discussion_r261462495
##########
File path: CONFIGURE.md
##########
@@ -0,0 +1,405 @@
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+ http://www.apache.org/licenses/LICENSE-2.0
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+# Apache NiFi - Configuring MiNiFi - C++
+
+## Configuring
+The 'conf' directory in the root contains a template config.yml document.
+
+This is compatible with the format used with the Java MiNiFi application. Currently, a subset of the configuration is supported and MiNiFi C++ is currently compatible with version 1 of the MiNiFi YAML schema.
+Additional information on the YAML format for the config.yml and schema versioning can be found in the [MiNiFi System Administrator Guide](https://nifi.apache.org/minifi/system-admin-guide.html).
+
+Additionally, users can utilize the MiNiFi Toolkit Converter (version 0.0.1 - schema version 1) to aid in creating a flow configuration from a generated template exported from a NiFi instance. The MiNiFi Toolkit Converter tool can be downloaded from http://nifi.apache.org/minifi/download.html under the `MiNiFi Toolkit Binaries` section. Information on its usage is available at https://nifi.apache.org/minifi/minifi-toolkit.html.
+
+
+ Flow Controller:
+ id: 471deef6-2a6e-4a7d-912a-81cc17e3a205
+ name: MiNiFi Flow
+
+ Processors:
+ - name: GetFile
+ id: 471deef6-2a6e-4a7d-912a-81cc17e3a206
+ class: org.apache.nifi.processors.standard.GetFile
+ max concurrent tasks: 1
+ scheduling strategy: TIMER_DRIVEN
+ scheduling period: 1 sec
+ penalization period: 30 sec
+ yield period: 1 sec
+ run duration nanos: 0
+ auto-terminated relationships list:
+ Properties:
+ Input Directory: /tmp/getfile
+ Keep Source File: true
+
+ Connections:
+ - name: TransferFilesToRPG
+ id: 471deef6-2a6e-4a7d-912a-81cc17e3a207
+ source name: GetFile
+ source id: 471deef6-2a6e-4a7d-912a-81cc17e3a206
+ source relationship name: success
+ destination id: 471deef6-2a6e-4a7d-912a-81cc17e3a204
+ max work queue size: 0
+ max work queue data size: 1 MB
+ flowfile expiration: 60 sec
+
+ Remote Processing Groups:
+ - name: NiFi Flow
+ id: 471deef6-2a6e-4a7d-912a-81cc17e3a208
+ url: http://localhost:8080/nifi
+ timeout: 30 secs
+ yield period: 10 sec
+ Input Ports:
+ - id: 471deef6-2a6e-4a7d-912a-81cc17e3a204
+ name: From Node A
+ max concurrent tasks: 1
+ Properties:
+
+### SiteToSite Security Configuration
+
+ in minifi.properties
+
+ enable tls
+ nifi.remote.input.secure=true
+
+ if you want to enable client certificate base authorization
+ nifi.security.need.ClientAuth=true
+ setup the client certificate and private key PEM files
+ nifi.security.client.certificate=./conf/client.pem
+ nifi.security.client.private.key=./conf/client.pem
+ setup the client private key passphrase file
+ nifi.security.client.pass.phrase=./conf/password
+ setup the client CA certificate file
+ nifi.security.client.ca.certificate=./conf/nifi-cert.pem
+
+ if you do not want to enable client certificate base authorization
+ nifi.security.need.ClientAuth=false
+
+You have the option of specifying an SSL Context Service definition for the RPGs instead of the properties above.
+This will link to a corresponding SSL Context service defined in the flow.
+
+To do this specify the SSL Context Service Property in your RPGs and link it to
+a defined controller service. If you do not take this approach the options, above, will be used
+for TCP and secure HTTPS communications.
+
+ Remote Processing Groups:
+ - name: NiFi Flow
+ id: 2438e3c8-015a-1000-79ca-83af40ec1998
+ url: http://127.0.0.1:8080/nifi
+ timeout: 30 secs
+ yield period: 5 sec
+ Input Ports:
+ - id: 2438e3c8-015a-1000-79ca-83af40ec1999
+ name: fromnifi
+ max concurrent tasks: 1
+ Properties:
+ Port: 10443
Review comment:
Don't need Port and Host Name for our RPG ports unless I'm missing a condition of using the context service
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services