Forum Replies Created
-
AuthorReplies
-
Ronald Ortiz wrote:
Now, what if you have the same MAC address but a different IP?
Does that affect the hcihostid?
No, it doesn’t. I didn’t
think it would, but I verified by changing the static address associated with the virtual machine on which I have Cloverleaf installed. The hcihostid command returns the same value as previously.Hi John, long time 🙂
Have you verified that you can actually establish an sftp connection to the site via the command-line sftp utility? The public/private key authentication has failed, and although it looks like password authentication has succeeded, I’m not sure you actually have access.
Try:
/home/hci $
sftp @emft.relayhealth.comReplace with the username supplied by RelayHealth.
If public/private key authentication still fails (it likely will), enter the password when prompted. If you get the
sftp> prompt, you’ve authenticated successfully.Next, try transferring a file:
sftp>
putIf that fails, I’d assume it’s a permissions problem on the RelayHealth side, or that you’re not in the right directory for file transfer. You may need to have RH set the home directory for that account to the proper directory or issue a ‘cd’ command to change to it.
If it succeeds, though, we’ll need to do some tcl debugging in the transfer script.
Hope this gives you something to go on.
January 28, 2015 at 8:25 pm in reply to: Received Email from LicenseKey.Care-Lawson@infor.com #81948Robert Milfajt wrote:True, but in this case we haven’t requested a license modification, so this message, which had spelling errors seemed suspicious.
January 28, 2015 at 3:31 pm in reply to: Received Email from LicenseKey.Care-Lawson@infor.com #81945Also received, and created an incident reporting its receipt in Xtreme. The headers seem right for Infor as the source, although there’s not much in the way of routing information.
I think they need to do a bit of scrubbing.
Peter Heggie wrote:So far I can’t find any images or pictures in the embedded help for Cloverleaf 6.1 – am I using the wrong browser? I’ve got IE 8.
The use of images is very spare, but there are some. For example, on my local Linux installation:
file:///opt/cloverleaf/cis6.1/integrator/docs/reference/engineinternals/engine_components.htm
Shows a simple block diagram of the engine architecture. From the TOC, it’s “Reference Guide | Engine Internals | Engine Components.”
[EDIT: Fixed link]
January 22, 2015 at 10:05 pm in reply to: Sending the same output to more than one destination #81870Thanks, Jim, it’s good to be here!
January 22, 2015 at 7:00 pm in reply to: Sending the same output to more than one destination #81868Makes sense.
Thanks, James!
[EDIT: And if I had actually read the OP’s message completely, I would have realized this :oops:]
January 22, 2015 at 3:54 pm in reply to: Sending the same output to more than one destination #81866Thanks for the followup, James; I appreciate it.
But I think I’m still missing something . . .
Duplicating, renaming and reconfiguring the outbound protocol threads and adding them all as destinations in a single route detail on a local test site took me about 90 seconds. Deleting those threads when done also removed the destinations from the route detail, so that was even faster than setting it up in the first place. It seemed pretty straightforward for either a temporary or permanent solution.
Perhaps the issue is that there are multiple inbound threads whose output needs to be replicated? My suggestion gets a bit more complex in that scenario, but in a linear fashion 🙂
Or maybe I’m just misunderstanding the terminology, given that I’m new here and an eGate refugee. My attempt didn’t involve creating additional routes, it simply added destinations to an existing route’s detail. If that’s bad form, it would be helpful to me to understand why.
Thanks!
PS. If the issue boils down to licensing, I guess I need to understand that better. It seems you’d need multiple protocol threads regardless.
January 22, 2015 at 2:18 pm in reply to: Sending the same output to more than one destination #81863Hi Everyone, long time eGater here but recently have joined the Cloverleaf cadre. My apologies if I’m missing something . . .
If the requirement is simply to duplicate existing output to additional threads, what’s wrong with creating copies of the existing outbound thread, renaming each copy and reconfiguring it for the IP address/port of the new downstream system(s), then adding them as a destinations in the inbound thread’s route detail?
-
AuthorReplies