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

FES Profile changes

Changes in FES profile to resolve eStudio Issues

Issue

Unable to login to eStudio from local machine while FES is running in cloud machine that has a public IP.

Resolution

To resolve this issue, you need to set the Public IP of cloud machine in the Hostname property present in FES profile.

Steps

Follow the steps below to set this property:

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

   2. Set RMIPortExportObjects to value of RMIServerPort(2047) property.

      Icon

      Default value for RMIPortExportObjects property is 2047 (For Fiorano10.2 and higher versions).

      
      
      Figure 2: Set Hostname and RmiPortExportObject
      
      

3. Save FES Profile.
   
   
   Figure 3: Saving profile
   
   

4. Start the FES server.

Changes in Connection Factories to Resolve Peer Connectivity Issue

Issue

When peer server is started in local machine and FES server is running in cloud, Peer server will not connect to FES server and will not start properly.
Connected to [URL: null] will be displayed on peer console.

Resolution

To Resolve this issue, we need to set the Public IP of FES machine in the FES server connection factories.

Steps

Perform the following actions:

1. Open FES profile in eStudio.
2. Go to connection Management perspective and Login to FES.
   
   
   Figure 4: Logging on to FES in ConnectionManagement
   
   
3. Go to FES > ConnectionFactories
4. For all connection factories, Change the Connection URL to http://<FESMACHINEPUBLICIP>:1847
5. For all connection factories set Auto Update to 'false' so that when server restarts, it will not reset the existing ConnectionFactory.
   
   
   Figure 5: Setting Connection URL and Auto Update
    
6. Right-click on FES and save configuration.
   
   
   Figure 6: Saving the Configuration
   
   

7. In Peer machine, clear peer DB and run FPS server.

   Icon

   In Fiorano 10.2 and higher versions this will be automatically taken care of by setting the mapped public ip address in FES profiles.

8. Go to Fiorano > esb > Transport  > FESTransportManager and set MappedPublicAddress property to FES machine public IP.
   
   
   Figure 7: Saving the Configuration

Changes required for Event Process not Starting while using Multiple Peers

Issue

When there is a route between component in fps running in local machine and component in fps1 running in cloud machine, event process will not start.

Resolution

1. Open FPS profile in Peer Machine eStudio.
2. Go to Fiorano > esb > Peer > Configuration > FPSCommonConfigLoader and set MappedPublicAddress property to public IP of peer machine.
   
   
   Figure 8: Setting MappedPublicIPAddress
   
   
3. Go to Fiorano > Esb > jmx > Connector > RMIBasedJMXConnector and set Hostname to public or private static IP address.
   
    

 

Message Slowdown in Sender

Issue

When one component is in fps which is running local machine and another component is fps1 which is running in cloud machine and a route is created between them, there will be message slowdown in the sender due to slow subscriber.

Resolution Steps

1. Open FPS profile in peer machine eStudio.
2. Go to Fiorano > mq > PubSub > TopicSubSystem and unCheck EnablePublisherSlowdown property
   
   
   Figure 9: Unckecking EnablingPublisherSlowdown
   
   
3. Save the profile

Editing Connection Factory

In addition to the steps mentioned above, edit the Output Port Connection Factory of the corresponding component which is created after launching the event process. Perform the following actions to edit the connection factory:

1. After launching the event process, login to FPS from Connection Management perspective .
2. Go to ConnectionFactories > <EPNAME>_<Version>_<COMPONENT_NAME> and click on Advanced Properties.
3. Set BatchingEnabled to false.
4. Save the configuration.

 

Changes in Connection Factories for Breakpoint and Reinjection Issues

Issue

Addition of break points and reinjection of documents will not work when Fes is on cloud and Peer Server is on local machine.

Resolution Steps

1. Open eStudio in FPS machine. Go to connection Management perspective and Login to FPS.
2. Go to FES > ConnectionFactories
3. For all connection factories Change the Connection URL to http://<FPSMACHINEPUBLICIP>:1867
4. For all connection factories set Auto Update to false so that when server restarts it will not reset the existing ConnectionFactory.

5. Right-click on fps and save configuration. 

6. Fiorano > esb > Transport > FESTransportManager and set FES machine public IP to 'MappedPublicAddress' property.

   Icon

   In Fiorano 10.2 and higher versions, this issue will be automatically taken care of by setting the mapped public IP address in FES profiles.

   
   
   Figure 10: Setting MappedPublicIPAddress

Changes in Local eStudio.ini file

Issue

Components colors does not change while connecting to FES running in cloud machine from local eStudio.

Resolution Steps

1. in FIORANO_HOME/eStudio/eStudio.ini file, add the below script:
   -Djava.rmi.server.hostname=<PUBLIC_IP_OF_eStudio_MACHINE>

2. Set the public IP of local eStudio machine to this.

   Icon

   9713 port (configurable), which is used to connect to FES, should be NATed to receive events from FES.

Ports

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