The configuration file can be found as ocsinv.conf, and we can edit it later on too. in Software Make Code39 in Software The configuration file can be found as ocsinv.conf, and we can edit it later on too.

How to generate, print barcode using .NET, Java sdk library control with example project source code free download:
The configuration file can be found as ocsinv.conf, and we can edit it later on too. use software code39 development tocreate barcode 3 of 9 with software Developing with Visual Studio .NET sudo vi ocsinv.conf The installation path of OCS agent on Mac OS X is on /etc/ocsinventory-client. As always, the agent can be executed manually. In this way, we are forcing an immediate inventory.

The following command under Mac OS X is used to do this:. sudo php /usr/local/sbin/ocs_mac_agent.php Please check the kind of tasks you have in the cron tab. By default, the installation package of Mac OS X agents installs the agent in the /Applications and sets it up as a daemon. The worst thing you can do is to set up another daily cron, even though the agent is run on every system startup.

This is not that bad, especially in the case of workstation computers that are not rebooted. Nevertheless, this is just a pointer, so we"re closely watching our actions. In case of troubleshooting, we can find the logfile at /var/log/httpd/error.

log. Please do find the problem (such as server gives a 500 error, perhaps a problem with the database, and so on). After a successful execution, the client will respond with an HTTP 200 message.

The 200 OK means Request is OK. Error messages often sport 500 as that stands for Internal Server Error. For a full overview of HTTP error messages, refer to the following URL:. As soon as we ge t a successful inventory run, we realize that it"s time to automate the process, especially if the computer is networked. We need to add a new task into the cron tab. Inventorying is usually advised to be run daily or 2-3 times a week.

It is possible to run the task more often, but this is rarely required. Under most circumstances, once a day suffices..

[ 90 ]. 3 . Here"s an exampl Software Code 3/9 e of a daily cron scheduled on 21:15. The agent is launched. We can edit the cron tab file using the crontab e command.

We need a new line like this:. 15 21 * * * /usr/local/sbin/ocs_mac_agent.php Deploying agents on mobile devices It is a rather n eglected process to make an inventory of mobile devices as well. This should not be the case with OCS-NG as we have this option too. We can set up the agents on mobile devices running Windows mobile platforms (version 5, 6+) and Java platforms.

On the devices running Java, we need to have a working Java virtual machine (JVM) supporting JDK version 1.4 or higher. Here we can mention IBM"s J9 JDK or phoneME, the open source project that aims to bring support for Java technologies on cell phones.

Let"s not get ahead of ourselves now, should you need more information, check out the following link..

net/. For handsets bas ed on Windows Mobile, ActiveSync is required on the computer. The successor of ActiveSync is Windows Mobile Device Center. One of these utilities is required for data synchronization between a computer host and a mobile device.

Getting these requirements installed and enabled are the preliminary steps. There is a lot of documentation available, and if we plan on doing something like this, the chances are that we already have these resolved. These should not give us headaches.

The name of the project that resulted in the porting of the inventory agent to mobile phones is called OCS Inventory Mobile. It was possible thanks to the OpenMobileIS, an open source Java framework for mobile applications. For more information, please check out the following link:.

Alright, now tha t we know how the ported agent came to life, let"s see from where we can download, and how to install on either Java-based handsets or WM platforms.. http://ocsinvent Code 39 Full ASCII for None ory.svn.sourceforge.

net/viewvc/ocsinventory/trunk/ mobile_devices/. [ 91 ]. The Zen of Agent Deployment In order to inst all the mobile agent on Java platforms, we need to generate a JAR file. We can either download a version that is hosted by someone, or we can make our own JAR exportation. To do this, we will need to download a Java IDE, such as Eclipse, checkout the official OCS Inventory SVN, and then we can export the project as JAR.

Other Java editors work too. The JAR file can be launched through the virtual machine on your system. Usually this command is something along the lines of Java jar path/ocsmobile.

jar doSynchro. Please refer to the user guide of your JVM. We can also check the following mobile installation guide:.

Copyright © . All rights reserved.