When i was introduced t0 JDE the first and foremost thing that
motivated me to go for becoming a CNC expert was that it gave me
opportunity to work on UNIX. Its beyond doubt one of the most
formidable platforms for any business and i was a lover since my early
college days :)
One of the biggest differentiating factors in Unix is its file system handling. People coming from the Windows world find it difficult to understand that the file storage has nothing to do with the drives they see in the explorer but is actually a mounted space allocated from the memory available. Its this “mounting” that makes any file system available for storage.
Syntax for Mount command is as follows:
$ mount /dev/hda3 /home
This command will “load” the resource or filesystem in disk drive hda3 into the local /home and then /home will have the memory on hda3 for use.
The best part of Mount is that you can not only mount hard drives connected to your server but use ones that are connected to the network as well. This is what is meant when some one says “the db client is a NAS mount”!!
Remember that there is no registry to be maintained in Unix and we don’t necessarily have to install an application on a particular machine to use it. It’s all about the Environment Variable and the file locations. So if you have an executable and the right parameters set for it in the environment variable, the executable knows how to take care of itself. It knows exactly where to look for the files it needs to execute.
Now when anyone says that the “db client is a NAS mount”, you can figure out that the DB client is installed on a different machine in the network and that particular drive is mounted in your Enterprise server and the Environment variables on your JDE Enterprise Server are set such that your server knows where to look for the DB client files when its trying to connect to the DB. As far as both the servers concerned are in the same domain and can reach each other in quick time, this works seamlessly.
The biggest advantage that this brings is maintenance of the supporting Applications. If the company has several hundreds of databases this architecture helps the DB support group to maintain all the db’s on their own servers and all the app teams can just mount the locations. Patching and maintenance is spared of the fragmentation and the upgrades can be handled much more efficiently.
If you want to check all the mount points that are currently there on your server execute the following command: more /etc/auto_direct
Have fun!!
Let me know if the post gives you a little bit of an insight on Mount as a UNIX feature. You can always check the man pages for details about any UNIX command. My intention over here was to drive away the initial fear of “what’s this!!” from anyone who is new to the world of Unix & CNC admin.
One of the biggest differentiating factors in Unix is its file system handling. People coming from the Windows world find it difficult to understand that the file storage has nothing to do with the drives they see in the explorer but is actually a mounted space allocated from the memory available. Its this “mounting” that makes any file system available for storage.
Syntax for Mount command is as follows:
$ mount /dev/hda3 /home
This command will “load” the resource or filesystem in disk drive hda3 into the local /home and then /home will have the memory on hda3 for use.
The best part of Mount is that you can not only mount hard drives connected to your server but use ones that are connected to the network as well. This is what is meant when some one says “the db client is a NAS mount”!!
Remember that there is no registry to be maintained in Unix and we don’t necessarily have to install an application on a particular machine to use it. It’s all about the Environment Variable and the file locations. So if you have an executable and the right parameters set for it in the environment variable, the executable knows how to take care of itself. It knows exactly where to look for the files it needs to execute.
Now when anyone says that the “db client is a NAS mount”, you can figure out that the DB client is installed on a different machine in the network and that particular drive is mounted in your Enterprise server and the Environment variables on your JDE Enterprise Server are set such that your server knows where to look for the DB client files when its trying to connect to the DB. As far as both the servers concerned are in the same domain and can reach each other in quick time, this works seamlessly.
The biggest advantage that this brings is maintenance of the supporting Applications. If the company has several hundreds of databases this architecture helps the DB support group to maintain all the db’s on their own servers and all the app teams can just mount the locations. Patching and maintenance is spared of the fragmentation and the upgrades can be handled much more efficiently.
If you want to check all the mount points that are currently there on your server execute the following command: more /etc/auto_direct
Have fun!!
Let me know if the post gives you a little bit of an insight on Mount as a UNIX feature. You can always check the man pages for details about any UNIX command. My intention over here was to drive away the initial fear of “what’s this!!” from anyone who is new to the world of Unix & CNC admin.
No comments:
Post a Comment