[bill bearden]

We are almost exclusively a Windows shop. So, we also run Cloverleaf on Windows servers. We used to install patches on all Windows servers every other month. A few months ago we went to monthly patching. We install the patches on all the test servers, wait about 10 days, and then install on the production servers.

While I’m not a huge fan of monthly patching (and usually rebooting), I can’t say we’ve had any more issues with monthly patching than bi-monthly patching.

[bill bearden]

Varun,

The default encryption key for SMATDB is the site name. Normally, we use this command to specify the key.

PRAGMA key=’yourkeyhere’;

Unfortunately, our firewall won’t let me post the command that worked here. It thinks I am attempting a SQL injection hack. But what I did in Windows was put the PRAGMA command before the SELECT command. I surrounded the PRAGMA;SELECT commands in double-quotes instead of the single quotes since the PRAGMA command really wants the key surrounded by single quotes. I’m not sure if you can make the same substitution in Linux.

Bill

[bill bearden]

Try a larger value in jvm_args=-Xmx

Was it a process that dumped? Or something else like hostserver?

[bill bearden]

Bryan,

Because people had different ideas at different times, we have used 3 different methods for sending email in Cloverleaf programs. Two are executable Windows programs: bmail.exe and POSTIE.EXE. We “exec” these in Tcl code. I wasn’t around at the time so I don’t know much about where those programs came from.

More recently, we have also used an all-Tcl method for sending email. Tcl comes with libraries for email (and lots of other things). The very basics look something like this:

Code:

 package require smtp
 package require mime
 set token [mime::initialize -canonical text/plain -string “Email body here.”]
 mime::setheader $token Subject “Your Subject Here”
 mime::setheader $token To “Firstname Lastname ”
 mime::setheader $token From “servername@company.com”
 smtp::sendmessage $token
   -recipients “firstname.lastname@company.com”
   -servers “emailServerNameHere”
   -originator “”
 mime::finalize $token
 unset token

The code above could have typos since I tried to simplify what we actually use. I also tried to give parameters that show what the format should be.

Bill

[bill bearden]

Jim,

If you mean multi-server, no.

I think that we didn’t need to because we set up the inter-site routing port on the ib. There is a “normal” connection from the registration system to the ib. Then there is a connection to the inter-site port from a destination thread in another Cloverleaf process.

Another way to have done it would have been to set up the ib as multi-server and made 2 “normal” connections. Probably the only reason I didn’t do it that way was that I wanted to try out the new features in Cloverleaf.

One factor to consider… When doing the inter-site port/Messages routed to this connection treated as inbound method, the messages that come this path don’t end up in the ib SMATDB. We have them in a SMATDB on a different thread. Sometimes, this is what we want. But sometimes you really would like all the ADT messages all in the same SMATDB.

Bill

[bill bearden]

We have this box checked on an inbound thread. The inbound that has it checked receives ADT messages from our registration system. The registration messages are routed to quite a few other systems.

But recently, another system needed to send ADT messages also. We send these new ADT messages to our registration system but the registration system doesn’t generate outbound messages when it receives messages. So we also send these new messages to the registration inbound thread using an “Inter-Site Routing Port” in Cloverleaf. This gets these registration messages routed to all the ancillaries that receive ADT from the main registration system.

[bill bearden]

Hello Mohammed,

The good thing about RTF is that at least it is printable characters. The bad thing about RTF is oh my gosh have you ever looked at RTF? 🙂 It isn’t very Tcl-friendly with all the backslashes and braces.

I have a couple of Tcl scripts that modify RTF in Cloverleaf. I use regsub. For example something like…

Code:

set Source {Efonttbl{Ef0EfnilEfcharset0 Microsoft Sans Serif;}}
set Success [regsub -all — {fcharset0 Microsoft Sans Serif} $Source {fcharset0 Courier New} Target]
if {$Success} {
   echo $Target
}

Good luck,

Bill

[bill bearden]

When I saw Max’s post the other day, I was hopeful someone would have figured out something cool. Our organization has just started the process of implementing some of the Atlassian products: Jira, Confluence, and Bitbucket. My boss asked me to work out how the interface team could use Bitbucket with Cloverleaf. I think Bitbucket is similar to Github in that it is a layer on top of Git that tries to make it a little easier to use.

I had already searched Clovertech and found some interesting topics. In 5782, Stephan Rubin states that (my paraphrase here) Git and Cloverleaf are not compatible because Git is very client oriented and Cloverleaf is server oriented. Stephan suggests having a workstation version of full Cloverleaf on each developers’ PC. But that would require different Cloverleaf licensing. And I don’t know if it would be worth the trouble just to say you are using Git.

I think I also read someone suggest that one could set up individual sites on the server for each developer and test environment. For example, we have currently dev and test sites on our test server. If each developer had had their own dev and their own test, they could work independently of all the users actually testing using the real dev and test. But when the code changes were good enough, they could commit in their own site and push to the “real” dev or test. But this doesn’t address deploying to prod.

In 7884, Paul Glezen mentions some of the issues with automated deployment to prod.

Also in 7884, Benjamin Rubin said he set up a script to do daily Git commits and then push to a central server. So far, that seems like the best suggestion.

[bill bearden]

We are on Global Monitor 6.1.1 and we have had AD security on it for quite a while. I don’t remember what version or when we turned it on.

We are on Cloverleaf 6.2.0.1 and we are testing Basic security/AD security. Our current impression is positive. I thought it might be more annoying but it doesn’t ask us for our passwords all the time.

I don’t know when the AD feature was added to the IDE but I think it was pretty recent. There is an LDAP tab in Server Administrator. The form is basically the same as the one in Server Administrator for Global Monitor.

[bill bearden]

Rob,

We are on Cloverleaf 6.2.0.1. We upgraded back in May 2017. At that time, we also moved from real hardware to virtual machines. I think it was at the same time (I don’t have that in the notes I quickly checked) that we upgraded to Windows Server 2012 R2.

So, I think we moved to 6.2 and Server 2012 and virtual hardware at the same time. It was more “new install” than “upgrade”. That is, we didn’t do an in place upgrade of Windows Server 2008 to 2012. The server guys created the servers and we installed the new Cloverleaf on them.

Look at the discussion on Performance Issues on 6.2. Our volume is a million messages per month, not a million messages a day. But we have had occasional performance issues in our biggest production site. We don’t know for certain that it is related to the performance issues in the discussion. But it seems likely. You might want to hold off until all 3 fixes are released.

https://usspvlclovertch2.infor.com/viewtopic.php?t=8484

While it was good to get all the changes (OS, Cloverleaf, hardware) out of the way at once, it leads to uncertainty when there are issues.

Bill

[bill bearden]

Bob,

I couldn’t find any messages that match your particular pattern so I can’t do a real test.

rPID|[^|]|[^|]*||

The idea is

1. rPID is what I use to make sure it is the PID segment

2. |[^|] should match any single char except a pipe in PID.1

3. |[^|]* should match 0 or more non-pipe chars in PID.2

4 || should match nothing in PID.3

Hope this helps.

Bill

p.s. A caveat is that this really assumes every message with a PID segment has values for at least PID.3. Step 3 above could bleed over into later segments.

[bill bearden]

Similar to Jeff but specific to JSON, something like

Code:

package require TclCurl
package require json::write

set URL “http://yourhostname:4949/”
set HttpHeader [list]
lappend HttpHeader “Content-Type: text/json”
set PostBody [::json::write object send_activation_email false]

set JSONResponse “”
set ReturnCode “”

set ReturnCode [curl::transfer -url $URL
               -post 1
               -httpheader $HttpHeader
               -postfields $PostBody
               -bodyvar JSONResponse]

produces something like

Code:

POST / HTTP/1.1
Host: yourhostname:4949
Accept: */*
Content-Type: text/json
Content-Length: 39

{
   “send_activation_email” : false
}

[bill bearden]

What do you mean by “‘normal’ POST format?

Are you just saying your JSON is missing the open and close curly braces? Or what?

[bill bearden]

Do you have to “package require sqlite” ?

[bill bearden]

We are a Windows shop and we have CIS on 3 servers. I looked at all 3 and one of them had a large box.log file. I guess we hadn’t ever created a BOX on that server. We had on the other 2 servers. After I created a BOX with just one thread in it, it appears the box.log file stopped growing.

So, as a work around, try creating a BOX.

[Author]

Replies