I am new to apache NIFI. I was kind of wondering where is the save button. I tried a sample from a tutorial that I saw on youtube. I would like to save all the processors that I created for future reference. I don't see any save button. Is is possible to save my work open later.? Or open in another machine.?
Please Help.
Apache NiFi automatically saves your flow for you. The flow configuration file is stored in ./conf/flow.xml.gz by default. NiFi also maintains an archive of previous versions in ./conf/archive. See the Core Properties settings for changing these settings. It is possible to backup and restore the flow configuration through these files.
Apache NiFi also has a Templates feature that makes it easy to save a selection from your flow, export it from the UI, and share it with other NiFi installations. Templates may be a closer approximation of a "save" button.
The Apache Nifi Registry is another option. You can version processor groups, commit changes to the registry, revert back, add comments, etc. I see it as similar to version control such as Git. It's helpful in collaborative settings as well as promoting changes from development to production.
Related
My question is this. I am using OBIEE 12c and recently I changed the .rpd file in offline mode and then uploaded it to the server. However I dont see my changes there.
Interesting is the fact that when I open the .rpd in online mode in Admin tool, which shows the current rpd in OBIEE, I see my changes. I tried editing in online or offline modes, changed the names of rpds, restarted the server, but nothing helped. What could be the reason?
EDIT.. It was my fault partially. I was making changes in BMM layer and I was pretty sure that my changes will be automatically updated in Presentation layer(it was when I checked with several aggregations), however in this case, my changes did not reflected in Presentation layer. Why is like this?
P.S. I was modifying hierarchies if important
I want to export/import only site structure not the content using Oracle WCS CSDT Plugin command line tool.
Basically, I want empty site to be created on production env without content, and content editors will publish content from staging once basic site is available.
Does anyone has an idea, how I'll do it?
I Think you can mirror the site which doesn't publish any content.
on admin tab, select the site you want and double click on it.
There you will see publish destinations. click on mirror site configuration for required environment and you can do it by selecting required things to mirror.
Well, I don't think this is the recommended way to do so, I actually think the CSDT tool isn't recommended by Oracle (will look up a source and amend my answer ASAP, just wanted to catch you before the irreversible happens).
Instead publish to the production environment from the current one, if it's not reachable you can publish to an installation on a portable machine (laptop or something) or maybe even a JSK (Jump Start Kit) on and the from the JSK to production.
Hope this helps.
Although its been one year, just to answer this question, I am pointing out what I did in my past projects:
I want to export/import only site structure not the content using Oracle WCS CSDT Plugin command line tool.
Yes, this is quite feasible to do so via command line or even by using ANT or maven script
Basically, I want empty site to be created on production env without content, and content editors will publish content from staging once basic site is available.
Once site is imported using CSDT, editors can publish. But note: asset types, attributes, etc. which were created using your local instance or JSK will have different asset id as compared to Staging instance.
Hence, rather than using CSDT, preferred way is to just initialize site and then mirror assettypes, attributes, attribute editors, etc. from Staging to Production and then publish attributes, etc. from Staging to Production. When production is ready with all basic configurations, editors can just publish content as they see fit.
We ship a config file as a part of our installation that we create via install4j. Suppose the user is doing an upgrade installation when we ship a new version of the product. Is there any way to determine if the user has manually modified the file after last installation ??
We need to detect if the user has modified this file, and then merge the changes that the user has done with the new changes that we are introducing by the update.
Any pointers / ideas would be greatly appreciated.
TIA
As of 5.1.11, install4j does not support this kind of content-based modification detection. Modification detection only takes file modification times into account.
Windows installer compares a file's create and modify dates. If they are different the file has changed.
I believe you can solve this in a better way by writing the config file using the main application executable using "internal defaults" in your application instead of a base config file delivered via your setup. You can then re-apply all internal defaults to the existing file, add any new updates whilst keeping user changes where possible (sometimes you want to override what has been changed?).
The more intelligent an application is in its configuration and maintenance of settings, the less deployment problems you will see.
I have set of JVM configured, WAS components (Queues, SIB, etc) created in one environment (WAS 8.0 ) and is all working fine. I need to replicate the same in another set of new servers (and another one potentially). How do I replicate all the steps without typing the information again?
Ideally, you'd make the original changes via scripting and re-run them. An alternative is "properties based configuration" for export/import.
http://www.ibm.com/developerworks/websphere/techjournal/0904_chang/0904_chang.html
May be very simple question for you guys. But I just want to clear my doubt.
I have seen option "Enable Version Control" while creating repository service. Can somebody tell me, what is the use of version control there?
Thanks in advance.
Nothing tricky here - if you choose this option, the repository will support versioning for all the objects, e.g. reusable transformations, mappings, sessions, workflows. You will have to check out the objects to edit them and then check them in, you will be able to view object's history, compare the revisions, revert changes, etc.