While using cloud environment to run Fiorano, you may require to make some changes in the profiles/properties/files to setup different modules in Fiorano. Some possible changes are detailed in the below sections.

FES Profile Changes

Managing Connectivity with eStudio

To enable login to eStudio from a local machine while FES is running in the cloud machine that has a public IP, set the Public IP of the cloud machine in the Hostname property in the FES profile. Perform the following actions to enable the same:

1. Stop the FES server if it is running and then open FES profile in eStudio on the cloud machine.
   
   
   Figure 1: Opening FES profile
   
   
2. Navigate through Fiorano > jmx > connector > RMIBasesJMXConnector and make the below changes:
   
   1. Set the Hostname to Public IP.

   2. Provide the RMIPortExportObjects property with the value of the RMIServerPort (2047 in the figure below) property.

      Icon

      Default value for RMIPortExportObjects property is 2047.

      
      
      Figure 2: Set Hostname and RmiPortExportObject
      
      

3. Right-click FES node and click Save to save the changes made in the FES Profile.

4. Start the FES server.

Enabling Peer Connectivity and allowing Breakpoints/Reinjections

When FPS server is started in the local machine and FES server is running in the cloud, following issues occur:

• FPS server will not connect to the FES server and will not start properly.

  Icon

  The following error message would be displayed on the peer console:

  Connected to [URL: null]

• Addition of break points and reinjection of documents will not work. 

Map the FES public IP in FES Profile to manage the above by following the steps below:

1. Open eStudio in the FES machine.
2. Go to Profile Management perspective and open the FES profile.

3. Navigate through Fiorano > esb > Transport  > FESTransportManager and set MappedPublicAddress property to FES machine public IP.

   
   
   Figure 3: Configuring MappedPublicAddress property

Running Event Processes while using Multiple Peers

When there is a route between a component in the fps running in a local machine and a component in the fps1 running in a cloud machine, event process (EP) will not start. Perform the following actions to make the EPs rn:

1. Open the FPS profile in the Peer machine eStudio.
2. Navigate through Fiorano > esb > Peer > Configuration > FPSCommonConfigLoader and set the MappedPublicAddress property to the public IP of the peer machine.
   
   
   Figure 4: Setting Mapped Public IP Address
   
   
3. Navigate through Fiorano > Esb > jmx > Connector > RMIBasedJMXConnector and set Hostname to public or private static IP address.
   
    
   Figure 5: Providing Hostname

 

Local eStudio.ini file Changes

Components colors may not change while connecting to FES running in cloud machine from local eStudio. In this case, add the following script in the FIORANO_HOME/eStudio/eStudio.ini file:

Ports

The following ports should be opened from the firewall in their respective machines and if public IP is used, they should be NATed from the public machine to the local machine.

Following is a list of ports that should be opened in the respective machines.