Opentaps Configurations
General Installation:
Installing opentaps ERP + CRM is fairly easy, and you do not need root user privileges. These instructions will help you get started running opentaps ERP + CRM on both Unix/Linux and Windows operating systems.
Prerequisites
The first step is to make sure that you have the correct Java Virtual Machine installed.For opentaps 0.8.x and 0.9.x, you must use Java 1.4.2. For opentaps 1.0.x, you must use Java 1.5. In both cases, you must use the Sun Java SDK, not GNU gcj which may have been supplied with Fedora Core or Ubuntu or the Java Runtime JRE supplied with Windows.
To determine what version of Java you are using, type the following command:
$ java -version
For opentaps 0.8.x and opentaps 0.9.x, you must see something like this:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_xxxx)
For opentaps 1.0.x, you must see something like the following:
Java(TM) 2 RuntimeEnvironment, Standard Edition (build 1.5.xxxx)
You must not see anything like
gij (GNU libgcj) version 4.0.1 20050727 (Red Hat 4.0.1-5) or anything that says "JRE".
If you do not see the correct JVM, you must go download it from Sun.
Next, you should unzip the opentaps ERP + CRM .zip file you have just downloaded and go into the directory where it is unzipped:
$ cd opentaps
Starting on Unix/Linux
If you are using a Unix/Linux system, you should make the startup scripts executable:
$ chmod u+x startofbiz.sh\\
$ chmod u+x stopofbiz.sh\\
IMPORTANT: If your system already has gcj and you just installed new Sun JVM, you must tell opentaps ERP + CRM to use the Sun JVM instead of the GCJ JVM in /bin/java by specifying where the JVM is:
$ export JAVA_HOME=/usr/java/j2sdk1.4.2_10/\\
(or whichever directory your Sun JVM was installed.) You can even put this directive into startofbiz.sh and stopofbiz.sh
To start the opentaps server,
$ ./startofbiz.sh\\ \\
The server is started as a background process, and the logs are piped to a file called "console.log" in the logs/ subdirectory
for opentaps 0.8.x and 0.9.x and runtime/logs sub-directory for opentaps 1.0.x To see the logs,
$ tail -f runtime/logs/console.log\\
or\\
$ tail -f logs/console.log\\
To stop the opentaps ERP + CRM server,
$ ./stopofbiz.sh\\
To start the Point Of Sales terminal, instead of using startofbiz.sh and stopofbiz.sh, use
$ java -jar ofbiz.jar -pos\\
Starting on Windows
IMPORTANT: If you are using Windows, you may run into problems with having paths with directories that have spacesin the name, such as "C:\Documents and Settings". You can avoid these problems by unzipping in your C:\ directory.
IMPORTANT: opentaps ERP + CRM runs as a server on your computer and needs to access a number of ports. If you are having start up problems, try re-configuring or temporarily disabling your firewall.
If you are using Windows, call up a command line terminal (Windows > Run Program > "cmd") From the terminal, go to your opentaps ERP + CRM directory
C:> cd c:\opentaps\\
You may need set a variable called JAVA_HOME first to tell Windows where Java is located:
C:> set JAVA_HOME=c:\java_1.4.2
Or which ever directory Java was installed in.
Now run the batch file to start the opentaps ERP + CRM server:
C:\opentaps> startofbiz.bat
The server will run in the terminal. Alternatively, you can create a Windows shortcut to the startofbiz.bat and place it on your desktop.
If you want to start the Point Of Sales system, use this command instead:
C:\opentaps> java -jar ofbiz.jar -pos
Error 1: You may be get such like error during start point of sales
2008-12-31 02:07:20,187 (main) No InterWiki reference defined in properties for Wiki called "XAConnectionFactory.java"! Can't get an XAConnection
java.sql.SQLException: Failed to start database 'ofbiz', see the next exception for details.
Solution 1: Then you need to stop OfBiz and problem will be fixed and then execute the above command again to start Point of Sales systems.
Mac OS X UsersA recent update to OS X 10.4.6 has made Java 5 the default JVM. To use Java 1.4.2 for opentaps 0.8.x or 0.9.x, set your JAVA_HOME to the correct path:
$ export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home
You can also use /Applications/Utilities/Java/J2SE 5.0/Java Preferences.app to set your preferred Java environment.
Accessing the Server
To access the opentaps ERP + CRM server, open any browser and type in the following: http://localhost:8080/You should see the opentaps ERP + CRM applications menu in your browser which shows you all the applications available.
You can now click on the application you wish to access. If you are using an older version of Sequoia ERP, you will need to access the applications directly using:
http://locahost:8080/ordermgr/control/main
for the order manager or http://localhost:8080/ecommerce/control/main
for the online store. Oh No! It Didn't Work! What Do I Do? Look in your runtime/logs/console.log and runtime/logs/ofbiz.log (or simply logs/console.log or logs/ofbiz.log files for opentaps 0.8.x and 0.9.x) and see what error messages are recorded. Check that you are using the correct version, that your database connection is successful, that there were no port conflicts, and that none of the required ports are blocked.
Signing In For the back end web applications, such as catalog, order, manufacturing, and facility managers, use the username "admin" and the password "ofbiz".
For the ecommerce online store application, use username "DemoCustomer" and password "ofbiz".
For the Point Of Sales application, use username "1" and password "1" for a manager and username "2" and password "2" for a cashier. What to do if you get an RMIDispatcher Error
If you see an error message like this:
Exception in thread "main" java.lang.NoSuchMethodError: sun.rmi.transport.Object
Table.getStub(Ljava/rmi/Remote;)Ljava/rmi/server/RemoteStub;
at org.objectweb.carol.rmi.jrmp.server.JUnicastRemoteObject.unexportObject(JUnicastRemoteObject.java:138)
at org.objectweb.carol.rmi.multi.JrmpPRODelegate.unexportObject(JrmpPRODelegate.java:94)
at org.objectweb.carol.rmi.multi.MultiPRODelegate.unexportObject(MultiPRODelegate.java:132)
at javax.rmi.PortableRemoteObject.unexportObject(Unknown Source)
at org.objectweb.jotm.SubCoordinator.doAfterCompletion(SubCoordinator.java:1548)
You are experiencing a problem instantiating the RMI dispatcher. The RMI dispatcher is used to call remote services
running on another instance of oopentaps. For demo purposes, you can usually turn this off by editing the file
base/config/ofbiz-containers.xml and commenting out the <containers> for rmi-dispatcher and rmi-print-server.What to do
if you get a BSH Error
If you see this error message:
java.lang.NoSuchMethodError: bsh.BshClassManager.createClassManager()Lbsh/BshClassManager;
at org.ofbiz.base.util.BshUtil.getMasterInterpreter(BshUtil.java:124)
at org.ofbiz.base.util.BshUtil.makeInterpreter(BshUtil.java:95)
at org.ofbiz.base.util.BshUtil.runBshAtLocation(BshUtil.java:144)
The problem is that your computer has another copy of beanshell (bsh.jar) installed in the Java class path. For example, OS X sometimes has a bsh.jar in /Library/Java/Extensions/ Simply move it out of the way and try again.
By,
Sharif Ul Islam
Senior Software Engineer
Mannaco Microsystems, Inc
www.manna-co.com

No comments:
Post a Comment