As many know, Go is a designed to build architecture and operating system specific binaries. These architecture and operating system specific binaries are called a target. One can target GOARCH=ppc64le GOOS=linux go build to build for the specific OS. There is a nice little tweak which considers the architectures version and optimizes the selection of the ASM (assembler code) uses when building the code.
To use the Power Architecture ppc64le for a specific target, you can use GOPPC64:
power10 – runs with Power 10 only.
power9 – runs with Power 9 and Power 10.
power8 (the default) and runs with 8,9,10.
For example the command is GOARCH=ppc64le GOOS=linux GOPPC64=power9 go build
3. Search for Event Streams, and click on Event Streams
Search and Click on Event Streams
4. Choose your Location. I chose us-south. Pick the data center that is closest or co-located with your IBM FHIR Server.
5. Select the Standard plan. A typical bundle which represents a patient history, such as Antonia30_Acosta403.json, include hundreds of resources which correspond to many messages sent over the topic when processed as a Bundle batch. For a Bundle transaction, you get only one notification message.
6. Click I Accept
7. Click Create. You are redirected to the EventStreams resource that is created.
Your Service is Created
8. Click Service Credentials
9. Click New Credentials
10. Click Add
Create Credentials Dialog
11. Copy the Service Credentials and paste it locally (on the right hand-side)
Copy Credentials
12. Click on Topics
13. Click Create Topic
14. Enter Topic Name – FHIR_AUDIT
15. Click Next
Enter Topic Name
16. Select the default number of partitions
Select Number of Partitions
17. Click Next
18. Select Message Retention – 1 Day
19. Click Create Topic
Create Topic
With the IBM EventStreams Kafka Topic setup, it’s now time to connect the IBM FHIR Server and the FHIR Audit module to Kafka.
You see the container id output 60a5f1cae6d677d80772f1736db1be74836a8a4845fcccc81286b7c557bc2d86.
26. Check that the applications are started using the container id.
$ docker logs 60a | grep -i started
[4/21/21, 20:55:58:449 UTC] 00000001 FrameworkMana I CWWKE0002I: The kernel started after 1.43 seconds
[4/21/21, 20:55:58:464 UTC] 0000002a FeatureManage I CWWKF0007I: Feature update started.
[4/21/21, 20:56:01:328 UTC] 00000030 AppMessageHel A CWWKZ0001I: Application fhir-openapi started in 1.588 seconds.
[4/21/21, 20:56:03:141 UTC] 00000031 AppMessageHel A CWWKZ0001I: Application fhir-bulkdata-webapp started in 3.402 seconds.
[4/21/21, 20:56:07:824 UTC] 0000002d AppMessageHel A CWWKZ0001I: Application fhir-server-webapp started in 7.871 seconds.
[4/21/21, 20:56:07:868 UTC] 0000002a TCPPort I CWWKO0219I: TCP Channel defaultHttpEndpoint-ssl has been started and is now listening for requests on host * (IPv4) port 9443.
[4/21/21, 20:56:07:880 UTC] 0000002a FeatureManage A CWWKF0011I: The defaultServer server is ready to run a smarter planet. The defaultServer server started in 10.885 seconds.
29. Scan the response.json for any status that is not "status": "201". For example, the status is in the family of User Request Error or Server Side Error.
