I have openldap on a linux machine. Is there a way to view the directory tree structure so I can see the DN's of users and how the directory is structured? I want to better understand the structure so it can help me form the right queries I am using in a script using the python-ldap module.
I use Apache Studio for such activities. But there are many others.
Related
I made some test sequences and a workspace in TestStand. I want to deploy those sequences and make a MSI based executable. However, I am not sure how can I include the files for Simple or Full Featured UI into the workspace and include it during deployment or call the UI content folder directly during the deployment.
Can anyone please help me?
Just insert folder with custom user interface into workspace https://www.ni.com/docs/en-US/bundle/teststand/page/tsref/infotopics/db_add_file_to_wksp.htm.
Then you will see inserted files in Deployment Utility.
But better practice would be to separate installers of user interface, and sequence itself. Because mostly you will do more changes/updates/fixes to sequence files, so you will need to redeploy just them.
This is a big undertaking, but may be worth it for you depending on the size of your company. TestStand has an API that you can use to develop a custom GUI. That GUI can then open any sequence file you like after being compiled as a C program that runs as an executable file.
I am trying to setup Basic Authentication for SOLR, and trying to follow their instructions: https://lucene.apache.org/solr/guide/6_6/basic-authentication-plugin.html
I created the security.json file, and now it says that I am supposed to put it in the $SOLR_HOME directory, if the instance is a standalone instance (which it is).
Where exactly is $SOLR_HOME? I googled to see that it's supposed to be where the solrconfig.xml or schema.xml file is, but because SOLR has multiple cores, those files exist in EVERY conf folder in EVERY core. So where is this file supposed to go?
$SOLR_HOME should be configured to point to the root of the cores and there should be a corresponding "solr.xml" in that location. You can copy the solr.xml from the Solr install directory under /server/solr/solr.xml
Edit: Clarifying what I mean by "root of the cores". The parent folder. If you have multiple cores; each core will be contained in it's own folder. The $SOLR_HOME is the parent folder to these.
$SOLR_HOME is where a new core is placed when it's created as well. In our case, the default install made that /var/solr/ with each core inside /var/solr/data/[corename].
Hi have an application running separateley (1 instance for customer) in different folders, 1 per each customer.
Each customer is a separate user on my machine.
At the moment I have the source code in each of these folders where I rebuild the code per each instance. Would it be better if I do something like the following?
create a shared folder where I build the code
deploy the binary in each user folder.
allow permission for each user to access the source code in READ ONLY mode.
when it is time to debug, by using gdb in each user folder will allow to read the source code and debug will happen.
Do you think that this could be a better approach or there are better practice?
My only concern is that each user has the chance to read the source code, but since the user will not access directly his folder (it is in my control) this should not trouble me.
I am using CENTOS 6.4, SVN and G++/GDB.
in different folders
There are no "folders" on UNIX, they are called directories.
I rebuild the code per each instance
Why would you do that?
Is the code identical (it sounds like it is)? If so, build the application once. There is no reason at all to have multiple copies of the resulting binary, or the sources.
If you make the directory with sources and binaries world-readable, then every user will be able to debug it independently.
I would like to ask some of you smart guys :) if it is possible to have directory structure in IBM Connections files. There is also library but i can't map it via webdav/smdb maybe it is about my information gap, but what I can is install desktop plugin ( only MS win) and then map my structure. But only files, no communities. And within files there cant be create directory in directory structure ( may i be wrong but i tried much and nothing changed my mind ). So if someone has ever experienced this before.
Can you guys help me?
While not as obvious as a File Repository like you experience in Windows Explorer. IBM Connections does enable you to use files / folders
You can find more information about the folders API at http://www-10.lotus.com/ldd/appdevwiki.nsf/xpDocViewer.xsp?lookupName=IBM+Connections+4.5+API+Documentation#action=openDocument&res_title=Working_with_folders_ic45&content=pdcontent
However, since you mentioned webdav, you may want to look at using CMIS and Apache Chemistry to access the CMIS APIs. That should give you the most flexibility in mapping your WebDav to Connections
http://chemistry.apache.org/
http://www-10.lotus.com/ldd/appdevwiki.nsf/xpDocViewer.xsp?lookupName=IBM+Connections+4.5+API+Documentation#action=openDocument&res_title=How_to_Use_Files_CMIS_APIs_with_Media_Gallery_ic45&content=pdcontent
An example of what you can do with CMIS is http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Demo_Using_CMIS_Connectors_with_Lotus_Connections_Files
The Files application does not support sub folders. Sub folders are available with IBM Connections Content Manager (CCM). CCM is an additional license but supports workflow and check in check out features as well.
In addition to Matt M answer.
CCM use FileNet P8 repository to persist the files, in this case you can start to use IBM Content Navigator client with Desktop Sync options, may be it will be usefull for your requirements.
Let say i have a cross-platform runnable application
This application create then read/write some data and preference in external files
Bundle hierarchy is as follow:
ApplicationFolder/application.jar
ApplicationFolder/database.odb
ApplicationFolder/config.xml
Whether it's on a Mac, Windows or Linux, the application knows that everything is next to her (ie: /database.odb or /config.xml)
Now comes the Self Contained Application feature provided by JavaFx 2
The application is embedded in .exe on Windows, .app on Mac and don't know yet about Linux...
As a Mac user i've tested it on Mac and saw that database.odb and config.xml are now created at the user root path
I thus agree that i should think of a cross-platform mechanism to save/read my application preferences regarding the operating system
But i'm not quite sure of what to do and how to do it (can't find any googling help either..)
On windows, the .exe is installed in a folder, so i guess i can keep the same behavior
On Mac, the .app is a folder and i should keep everything inside (how to get the .app path ?!)
Isn't there a built-in mechanism in Java/JavaFx ?
Thanks a lot for any comment, advice, documentation or else that you could give me
Badisi
There are many ways to do this. I have listed some of them here in no particular order. The recommended approach depends on the type of data being stored.
Java provides a couple of mechanisms (e.g. the properties API and the preferences API) for maintaining application preferences.
If your application is sophisticated enough to benefit from an database, then you might want to use Java EE or Spring, both of which have their own configuration mechanisms.
For read-only configuration, you can bundle the relevant files inside your application jar.
To store customized application configuration files or client application wide databases in relative to the application jar, write the required files at runtime. See How do I get the directory that the currently executing jar file is in?.
For user specific configuration, use System.getProperty("user.home") to retrieve the user's home directory, then create a subdirectory for your preference storage (for example "{$user.dir}/.myapp") with hidden file attributes so that it doesn't show up on a standard file directory list.
If your app relies on internet connectivity, then you can store some of this information server side rather than the client and make use of it from the client using internet protocols. An advantage of this approach is that user configuration and data is automatically ported across client machines.