Edc batch question

[alohaakamai3]

I have a slightly older version of aloha that's timing out on large batches over the internet. The internet does really not seem to be a the problem. But we hooked up a back modem. The problem is, the modem is basically starting the batch from scratch again, not picking up where the internet left off. The processor doesn't like it and says it's a duplicate.

I'd really like the cards to authorize over the internet, and settle using our phone line. That would be a workaround I can live with. Does anyone know a batch file or some other trick i can employ other than stopping Edc and unchecking the option to process online so the modem would batch?

Thanks!

 

[coorsman]

What vision of aloha?

Cheers,
Coorsman

 

[alohaakamai3]

Coors-

5.3x... not sure of exact release, but I can find out.

Ideally I would like to fix it, but I know there are commands used to automatically batch, I wondered how big a stretch it would bet to have a batch file that authorizes over the Internet, to settle over a modem.

 

[coorsman]

there are additions to the edc.ini file that will allow longer timout's for ssl connecitons. What rocessor do you use?


Cheers,
Coorsman

 

[alohaakamai3]

Visanet- I think there is one now that has is:

WaitForSSLResponseMessageTimeout=150

and

WaitForResponseMessageTimeout=80

I assume one is for the modem and one is for the Internet processing?

They're in the [Store] section of ini.

I noticed in another thread gunstar was saying certain router brands will close the connections?

 

[RokStar]

tricky.. and I don't know if I would do this, but...

Your "settle" program could stop EDC, replace the ini with one that only does dial-up, start edc. copy the req, settle the batch, then repeat backwards to put a SSL ini back in place for next day.
I would put many checks and logging in along the way. But in theory, this would work.

 

[alohaakamai3]

That's actually not a bad thought, thanks. It's a little rough around the edges, but not knowing exactly all the command lines that EDC could use, I agree your idea should work.

Does anyone know off hand what the line to remove the SSL settle from the ini file?

Also, does anyone have a list of available command lines that could be used with edc?

 

[RokStar]

There aren't any command lines that I know of. Why are you needing any?
As for the ini, just make a new EDC ini using the GUI.

Check the "Use SSL" box, there's one.
Uncheck the box, there's the second ini.

Save both separately because you're going to be copying them back and forth, every night. Then make backups of your backups, and then test, test, test, test, test, well you get the idea.

 

[alohaakamai3]

To make it so it's not clumsy, I would think I would need command lines.

I assumed I would need a command lines to stop edc and start edc... which I could probably do by stopping the service, but that will make an error message pop up. And then I would want it to also settle, all in one click (could use the settle instructions from the automatically settling batch file from years ago). Then it would have to wait for the batch to be done (a wait command that waited like 10 minutes would be fine), and copy the old edc.ini after.

I wonder if you really would have to stop edc at all to recognize new ini or would it adapt to it without stopping and starting.

Remember, for you a I, an extra step is not a big deal- for an end user... well, different story

 

[alohaakamai3]

I see what you're saying though- user clicks batch file.

Settles manually.

User clicks batch file.

Done.

I was thinking of a one click solution, that's all.

 

[RokStar]

even easier.

Winhook runs a batch file called "Settle"

Settle:

TASKKILL /F /IM EDC.EXE
NET STOP EDCSVR
COPY /Y <DRIVE>:\<FOLDER>\EDCdial.ini %IBERDIR%\EDC\EDC.INI
NET START EDCSVR
WAIT 30
COPY %IBERDIR%\<FOLDER>\1000001.REQ D:\ALOHA\EDC\*.*
:WAIT
WAIT 300
::Where the above "300" seconds is the longest a batch could take.
:: figure out a way (Sorry I don't have time right now) to see if <dob>.stl exists and keep checking until it's found. If it's not, GOTO WAIT
:SETTLED
NET STOP EDCSVR
COPY /Y <DRIVE>:\<FOLDER>\EDCssl.ini %IBERDIR%\EDC\EDC.INI
NET START EDCSVR
exit

 

[posrescue]

Don't forget that Visanet interface in EDC requires a correct value for the transaction number and the correct batch number in the ini...

 

[RokStar]

Very good point. I forgot about that.
After you settle, then copy the ini BACK to your "holding area",
you can just use the same ini every night, and it will bump that batch number for you each day. (This is why testing is SO important.)

 

[alohaakamai3]

I hadn't thought of that either, and yes, testing is really critical. Ironically, I went with a slightly different approach for a completely different reason, but it was identical in concept.

Not unlike that batch sequence #, The LAST SETTLEMENT DATE in the interface would always remain the same. I thought that might create confusion.

So I went to find out what changes in the ini when going from Internet to modem, and figured I'd find a way to modify that instead. As it turns out, the only thing that changes in the edc.ini when you go from modem to internet is a line called SSL=1, which will become SSL=0.

Apparently, using standard DOS commands to try to edit an text file is somewhat complicated. But, I found a utility called Change.exe online that allows you to do "search and replace" strings in text files. So, instead of copying the Edc.ini file,the batch file executes CHANGE, which looks for SSL=1 and changes it to SSL=0. Then the EDC service restarts and the req file drops in. And then does the opposite when the batch has settled, so it can go back to processing online.

Thanks guys, for your help, my DOS syntax was a little rusty and you saved me some time and frustration. I think it's working, a little more testing to do, but just about there.

The only minor issue I'm having now is when I run edc.exe to restart the interface at the very end of the file, it won't execute any more commands. I wanted the batch file to exit, and it stops- EDC launches fine, but won't proceed to the exit command I have waiting after Edc.exe.

Any ideas on that one?

 

[RokStar]

it should start with either CALL or START.
I think it's START %IBERDIR%\BIN\EDC.EXE
one of those commands will start the exe but not wait for a return.

 

[alohaakamai3]

Thanks, START worked (call did not- launched it, but same result of halting the execution).

I was hoping to have the file call the EDC interface right before the req was dropped, so the user could actually see transactions being process like they normally would, but apparently this method bypasses the user interface altogether.

 

[RokStar]

This is for automatic settlement at winhook, yes. I haven't had any reason for a manual settlement, or the need for anyone to watch it in years. These are just ideas, remember. Every env. is different.

 

[alohaakamai3]

Yeah, I am little old in school in that I like someone to be responsible for it. We do have some non-Aloha stores that have a processor initiated settle, and they have not been a problem. But there is a small part of me that always worries everyone could just assume it's going through if they never check it with. This can go on a little longer than you'd think in bigger companies.

Because this is a problematic location we're dealing with, it's going to be a batch file that actually has to be clicked on for now.

Still, I was surprised it didn't show the info going through via the EDC screen.

Asking it to look for a .stl file using an IF statement is definitely way I would go, but it's a little beyond me right now.
For now, I simply put an IF statement that checks the EDC\Processor folder for tnx.** about 5 minutes after the batch is started. If there isn't, it goes to a screen that more or less says: If looks like it's good, check LAST SETTLE and EDC reports to verify.

If it does find txn, it goes to a different DOS screen that turns the color red and says: Warning! There appear to be transactions.. .blah blah blah....


Of course, like you said before... test, test, test ... which I haven't done a ton of yet. There may be something that makes the whole thing not work, or an exception where there would be txns in the folder after batch. I can't think of any, but time will tell.

Seriously, you were a huge help man, I appreciate it.

 

[eburks]

I'm just blundering in without carefully reading the whole thread so appologies in advance...

If you need to make changes in an existing INI file via a batch script there is a program called minitrue that will allow you to do some fairly sophisicated search and replace things automagically. google it or

http://www.idiotsdelight.net/minitrue/

Seems like your in good hands with the folks in this thread and on that note I am going to throw something out that I will also put in a separate thread

I want to run a BOH and FOH that do not have administrative users logged in. I have had success on 5.3.31 running BOH with no admin priveledges but have never succeeded getting FOH to run that way.

Any tips or success stories here