Acomba

2018-05-30T21:28:27Z

Zfreeman: A GL integration between Acomba and ITrack Enterprise

= Acomba Integration =
== Installation ==
The necessary files can all be found through SVN at SVN\Trunk\Utility\Scripts\DuboisAcomba.
# Run acombaGLView.sql and custom_inventory_triggers.sql on their itrack enterprise database.
# Install python 3.4 and the python mysql connector, ensuring both 32bit or 64bit.
# Create a folder called AcombaExport in the ISoft Data Systems folder in program files, where the enterprise folder exists. Copy the glExport.py file and the PythonTools folder into your new folder.
# Create a task in Windows Task Scheduler to run the export on whatever schedule the client would like. The executable will be python, the argument will be ./glExport.py and the working directory should be the folder you created in step 3.
# In the glExport.py file, there will be a line at the beginning indicating the folder it writes files to as well as the mysql credentials. Ensure both are valid and what the client wants.
== Operation ==
Grab the most recently created export file in the path specified in glExport.py.
Ask the client to open Acomba and login.
Import the file in acomba by clicking on the menu>Input>Utilities>Import Data, select the "Transactions to the General Ledger" radio button, then click import and select the file.
If there were errors, view them. Note that old errors are not automatically deleted, it's all just saved to a file in the export folder called GLIMPORT.ERR, so you may see errors that were generated long ago. Renaming or deleting the error file can help clear out the noise.
== Summary ==
The python script simply reads from the view v_acomba_glexport, which contains all unexported gl information. This information is formatted in the fixed width manner required by acomba and written to a date stamped file. It then marks all glentries as exported in the enterprise database.

Using SVN from the command-line

2016-04-15T18:23:48Z

Zfreeman: /* Update */

This document explains the three most important SVN commands that you can use from a command line. It doesn't deal with questions you may have about how to use TortoiseSVN, ISoft's favorite SVN tool for Windows.

Although SVN is a command-line program, it is also context-sensitive. In other words, SVN assumes that you want to operate on files in the current directory, so you should change directories to your "working copy" before getting started.

You run SVN commands by typing 'svn', followed by the command, followed by the command arguments.

== Checkout ==

Before you can use or work on a product that is stored in SVN, you need to check it out. First, you need an SVN username and password, and you need to know the URL of the files you are checking out. (For example, ITrack products are kept in <nowiki>https://svn.isoftdata.com/ITrack/trunk</nowiki>, LXE is kept in <nowiki>https://svn.isoftdata.com/Web/trunk/EnterpriseLX</nowiki>, etc.

Then, create a folder for your local "working copy" of the product, go to the folder, and enter 'svn checkout' followed by the URL, like this:

<pre>
svn checkout https://svn.isoftdata.com/Web/trunk/EnterpriseLX
</pre>

This command will check out all the files needed for running LXE on a given server. (Note that LXE is not ready to use out-of-the-box like this; in order to prepare LXE for actual use follow the steps for [[Installing LX]].)

== Update ==

If you have already checked out files in the past, and you want to update those files based on what is in the SVN repository, you use the 'update' command, like this:

<pre>
svn update
</pre>

If there are conflicts between files, you may need to choose between the version of the file that is in the repository ("tc") and the version of the file that is stored in the current directory ("mc"). Otherwise, you may wish to hand-carve the local file based on the differences between it and the one in the repository ("ec"). If you just want to '''see''' the differences, type "df" at the question prompt. (For details on the 'diff' command, including how to read its output, enter 'man diff' from a linux prompt.)

If you're changing things in production, before making any commits, please run the following to see local changes from your last checkout.
<pre>
svn stat
</pre>
The command to see differences between your local copy and what's currently on svn is as follows:
<pre>
svn stat -u
</pre>

Please check both of these things before committing to production.

== Commit ==

You may wish to upload local changes to the repository, creating a new revision that reflects those changes. To do so, you must first ensure that the local copy has been updated (see UPDATE above). Then, commit your changes like this:

<pre>
svn commit
</pre>

SVN may ask you to enter some comments in a text editor regarding your changes; you can enter comments or just type :wq to submit your changes without comment.

== Conclusion ==
These are the three day-to-day operations you will likely want to use from the command line. For more detailed information about using SVN, you may wish to read [http://svnbook.red-bean.com/en/1.5/index.html Version Control with Subversion].

ISoft Wiki - User contributions [en]

Acomba

Using SVN from the command-line