We are going to be implementing a storage...
Articles and Tips: qna
01 Nov 2002
Q.
We are going to be implementing a storage system for our students. We need the ability to bulk-load anywhere from 4,000 to 10,000 students into eDirectory and set up home directories on Netware servers. I would use something like ICE, but it does not support creating home directories. I would look at uimport, but it doesn't support home directories over eight characters.
In looking at other third-party options, we felt that the cost was not justifiable to purchase a solution. That it may be better to create an application in-house to do this that can better integrate with our systems.
I am wondering how difficult would it be to create an application to do the following in Java. Pull student information from a SQL-compliant server, create the users, set a password, set attributes such as full name and phone number, create a home directory, assign the home directory trustees, and assign a volume quota to the user. I understand for some of you this may be easy. I put my Java skills at good, but I am not an expert. I have made small java applications that query SQL servers and print to printers, but nothing like this.
In looking around on http://developer.novell.com, it seems to me that I would need to look at NJCL for the file system end of this program. Is that correct? Also, if I used Novell Java Class Library (NJCL) and not NJCLC would, I not have to worry about authenticating to eDirectory, since I would be already with the client?
I am also curious to know what other tools I may need besides NJCL (if even NJCL) to achieve such a task. Also, any information that I should watch out for, etc., would be very helpful.
A.
Yes, the only Java solution to access files (in order to take advantage of NetWare's file system abilities) is through NJCL. It can do all the things your application requires. Now, deciding which NJCL to use (NJCL standard or clientless) depends on were your application is supposed to run. If it is to run on a NetWare server or on a Windows machine (with Client32), then the standard NJCL would work. But if your application needs to run in another OS (like Linux, Solaris, or Windows with no Client32), then you would need to use the clientless version. For better performance, I would suggest you use the standard NJCL, specially when you have to deal with 4,000 to 10,000 users.
Regarding its difficulty, it should be a relatively straight forward application. But if you're not familiar with JNDI specifications (Java Naming and Directory Interface), things may look a little be different than what you expect. Also, if you're planning to run your NJCL application on an already authenticated Windows machine (with Client32), you don't need to authenticate again in your code. Besides the NJCL libraries, you may need the SQL libraries to access your database (you could also use JDBC which is already included in the JDK). Other than that, you won't need anything else.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.