I *believe* I can safely do the following to my test and live instances command line;   

1. login to terminal

2. zn "PRODUCTION"

3. do ##class(%SYS.Maint.Bitmap).OneClass("Ens.MessageHeader",1,0)

I'm checking with WRC

Added questions:

• Should the foundation production be used as a Interoperability Production or a routing Production? 
• Are Interoperability and Routing productions the same thing?
  • I am coming from ensemble where you build all your interfaces all in a single production. 

Hi, 

wrc just confirmed that externally created certificates can't be signed using the IPKI

If you need to sign a certificate request to create a client certificate, you can use openssl:

 openssl x509 -req -days 365 -in [client]request.crs –signkey YOUR-CAprivatekey.pem -out [client].cer

This uses your private key to sign their certificate request to create their client certificate.

 You should send your CA certificate (not the private key) and the signed client certificate back to the client.

Thanks

good point about SHA1 

- this is brilliant:

I:\Projects\certiificates>openssl x509 -text -in certsForStunnel.pem -noout
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            af:0c:7a:b9:44:11:6c:e8
    Signature Algorithm: sha1WithRSAEncryption
        Issuer: C = GB, ST = West Somewhere, L = Town, O = XXX, OU = HL7, CN = VENDOR HL7 Messaging API
        Validity
            Not Before: Apr 13 10:48:24 2017 GMT
            Not After : Apr  7 10:48:24 2042 GMT
        Subject: C = UK, ST = London, L = London, O = LNWH NHS Trust, CN = TIE
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:e0:24:df:16:3d:d4:ed:1f:b0:4a:2b:6a:07:a7:
[truncated]

Suriya at WRC solved this for me

Where I went wrong: 

1. I created context.pidSegment as EnsLib.HL7.Segment - which fails as an argument to the DTL <assign> statement)
2. I forgot the (1) in {PIDgrp(1).PID}

The right way to copy a segment from one message to another is;

1. create context variable as a string:  e.g. context.pidSegment as %String(MAXLEN=2500) 
2. extract the segment as a string: context.k22.GetValueAt("PIDgrp(1).PID")
3. use the DTL to set the right field: <assign value='context.pidSegment' property='target.{PIDgrp(1).PID}' action='set' />

Thanks go to Suriya at WRC

Stephen

As it stands there is no known way to specify the full class path to a utility function.

Alternatives are discussed in the other comments below.

Whitelist for Atelier.

• *.eclipse.org
• atelier.artifactoryonline.com  (soon to be retired)
• atelier.jfrog.io  (new domain for *.artifactoryonline.com domains)

This might be help if (like me) you work at a hospital with very strict network security.  Without whitelisting these domains for my team, the proxy (Trend) detects the JVM binaries and automatically blocks traffic.

The kind staff at the WRC helped me with this question. (WRC staff are amazing)

Thank you to the community members who responded and Andrew Harris of InterSystems UK(WRC)  

I have combined the question and answer I received from Andrew and the community as an article: 

https://community.intersystems.com/post/speeding-source-and-target-drop-downs-message-viewer 

A foundation production is an interoperability production.  The wizard creates the namespace and production and adds it to a register of healthshare productions visible on the wizard screen.

The Ens.Activity.Operation.Local operation is used to collect/monitor production activity. See Monitoring Productions Monitoring Activity Volume for details. 
 

To summarise; 

• The 'Configure Foundation' option in the Installer Wizard;
  • creates a healthcare interoperability namespace and production 
  • adds this production to the register of productions on the Installer Wizard page
• A Foundation Production is just an normal interoperability production
  
  • it is only critical in the sense that you need one to process messages in HSHC. 
  • it is the same as a HL7 routing production created with the Production Wizard except that it doesn't pre-populate with; HL7FileService, Ens.Alert, MsgRouter, BadMessageHandler,EMailAlert, HL7FileOperation and PagerAlert.
  • it does include a Ens.Activity.Operation.Local operation (see Monitoring Productions Monitoring Activity Volume)
• HSHC 2019.1 also creates a Foundation Production and adds it to the list on the Installer Wizard page when you tick the 'enable names for interoperability productions' tickbox. (ticked by default in HSHC 2019.1)

Advice:

• use the 'Configure Foundation' option in the Installer Wizard to create interoperability namespaces and their associated productions
• manually create whatever you need from HL7FileService, Ens.Alert, MsgRouter, BadMessageHandler,EMailAlert, HL7FileOperation and PagerAlert  
• don't manually create interoperability namespaces and productions. use the wizard.
   

Notes:

• the old 'New production' dialog doesn't add your production to the list of configurations defined at  http://yourserver.etc:port/csp/healthshare/HS.HC.UI.Installer.Welcome.cls
• The 'start all' button wont start your new production, it will start the foundation production created when you created your namespace, or throw an error if you deleted it. (hitting 'stop all' stops all productions even if the are not in the 'register')
• WRC informed me that the Ens.Activity.Operation.Local operation will be removed in future versions. I don't know what that means for the Monitoring Productions Monitoring Activity Volume functionality?