Configuring a Front-End Processor (FEP) on Your Live Energy Connect Cluster

Oracle Utilities Live Energy Connect can be configured to act as a Front-End Processor for Oracle Utilities Network Management System Flex SCADA system allowing it to send messages to the client.

The Oracle Utilities Live Energy Connect 25.12.0.0.0 message bus is configured by clients (for example, Oracle Utilities Network Management System (NMS) Flex SCADA) that send configuration information to LEC. From the client's perspective, Oracle Utilities Live Energy Connect 25.12.0.0.0 acts as a Front-End Processor (FEP) for the client.

Note: A single Oracle Utilities Live Energy Connect 25.12.0.0.0 cluster can host multiple FEPs. For example, NMS Flex SCADA users will use the Oracle Utilities Live Energy Connect 25.12.0.0.0 cluster's various applications by creating a FEP in NMS and configuring it to the connect to a particular FEP service running on the Oracle Utilities Live Energy Connect 25.12.0.0.0 cluster. The FEP service (for example, "fep7-grpc-service") running on the Oracle Utilities Live Energy Connect 25.12.0.0.0 cluster will then create and manage the resources requested by NMS Flex SCADA. By default, no FEP services are deployed on your Oracle Utilities Live Energy Connect 25.12.0.0.0 cluster. The FEP service needs to be initialized with a specified, unique FEP ID that may vary depending on the client's configuration state.

Note:

See the Oracle Utilities Network Management System User Guide Flex SCADA chapter for information on configuring FEPs with NMS Flex SCADA.

Use the following steps to create and configure a FEP on the Oracle Utilities Live Energy Connect 25.12.0.0.0 cluster so that a client, such as NMS Flex SCADA, can use the FEP service. These steps will install the FEP service on the cluster and configure the required nginx service configuration and firewalld configuration on the nodes in the cluster.

Add a FEP Service on Your Oracle Utilities Live Energy Connect 25.12.0.0.0 Cluster

On the OCNE localhost (the host from which the OCNE cluster was created), run the following steps:

Open a Bash shell session and change to the directory where the lec run file was previously unpacked. This process creates a directory with a name similar to installer_25.12.... Change into that directory, and then change to the scripts subdirectory.
The create-fep-on-ocne2.sh file should be present there. For example:
```
[lec@ugbu-phx-1147 ~]$ cd installer_<release-version>/scripts/
[lec@ugbu-phx-1147 scripts]$ ls -al
-rwxr--r--. 1 lec lec 25561 Dec 12 20:56 create-fep-on-ocne2.sh
```
Run the following command:
```
./create-fep-on-ocne2.sh --id <fep_id> --port <port_number>
```
Where <fep_id> is the unique numeric ID assigned to the FEP service by NMS Flex SCADA, and <port_number> is a currently unassigned port (configured in NMS Flex SCADA) on which the FEP service shall listen.

For example:
```
./create-fep-on-ocne2.sh --id 7 --port 50051
```
You will be prompted to press Enter to continue with this step.

Note:
You can also exit by pressing CTRL + C.