Page History

...

Sample configuration to launch EAI Demo sample is shown below. The user needs to take care of populating required variables mentioned in the readme file. Batch scripts can also be used to provide these values which is discussed at the end of the section.

Image Modified

When the command is executed, the task prompts for the username and password and launches the Event Process(es). The password can also be provided in connection.properties to avoid the prompt or it can also be provided directly in batch files.

Sample screenshot is shown below for launchEStudioApps. During the first run it has prompted for the password and in the second run the password is picked up from connection.properties file (CONNECTION_STRING=tsp_tcp://localhost:1947;admin;passwd).

Image Modified 

Stop Application

Same as startEStudioApps, but the following properties have to be provided in eStudio.properties file.

Image Modified

Sample scripts are provided below.

...

1. Run FES server necessary for export application process.

2. Set properties directory to which application zip files are to be exported and the list of applications to be exported in eStudio.properties file:
   _ESTUDIO_APPLICATION_EXPORT_DIR=/temp/import_ESTUDIO_EXPORT_APPLICATION_LIST=SIMPLECHAT:1.0,EVENT_PROCESS1:3.0

   Info
   If the mentioned directory does not exist, the function creates it.

3. Run command "ant exportEStudioApps" in CLI_HOME. Refer Figure below for sample output.

   Image Modified
   Sample output for export Applications

...

1. Run FES server necessary for import application process and have the application zip file to be imported in the local disk.

2. Set properties, directory from which application zips should be taken and the zip file names in eStudio.properties file:
   _ESTUDIO_APPLICATION_IMPORT_DIR=/root/import/ _ESTUDIO_IMPORT_APPLICATION_LIST=SIMPLECHAT_1.0.zip,WORKLIST_MANAGER_1.0.zip

3. Run command "ant importEStudioApps" in CLI_HOME. Refer Figure below for sample output.

Image Modified
Sample output for import Applications

...

1. Set properties export directory, applications to be exported in eStudio.properties file.
   _ESTUDIO_EXPORT_APPLICATION_LIB_LIST=SIMPLECHAT:1.0,EVENT_PROCESS1:3.0_ESTUDIO_APPLICATION_EXPORT_DIR_LIB=/temp/import
2. Run command "ant exportEStudioAppsWithLibs" in CLI_HOME. Refer the below figure for sample output.
   
   Image Modified
   Sample output for exporting Applications with Libraries

...

1. Set properties import directory and the files to be imported in the directory:
   _ESTUDIO_APPLICATION_IMPORT_DIR_LIB=/temp/import_ESTUDIO_IMPORT_APPLICATION_LIB_LIST=SIMPLECHAT_1.0.zip,EVENT_PROCESS1_3.0.zip
2. Run command "ant importEStudioAppsWithLibs" in CLI_HOME. Refer Figure below for sample output.
   
   Image Modified
   Sample output for importing Applications with Libraries

...

1. Set properties for single application folder name, svn revision (HEAD indicates latest version), a temporary directory to which application is checked-out in eStudio.properties (also set SVN details in svn.properties):
   svn.username=usersvn.password=passsvn.repository=/trunk/application_ESTUDIO_SVN_IMPORT_APPLICATION=event_process10-1.0_ESTUDIO_SVN_IMPORT_APPLICATION_REVISION=HEAD_ESTUDIO_APPLICATION_IMPORT_DIR=/temp
2. Run command "ant importApplicationFromSVN" in CLI_HOME. Refer the figure below for sample output.
   
   Image Modified
   Sample output for importing Applications from SVN

...

1. Select all the components.
2. Go to Properties > Deployment > Nodes

3. Set the peer name to fpsQA
   

   Info
   Multiple peer names can be specified as comma separated values like fpsProd, fpsProd_BackUp

   
   
   

4. Save the Event Process. Once the Event Process is saved, notice the peer names being reflected in the Environment Properties of the Application as highlighted in the below image.
   
   

...

1. Set properties application to import, components to import, source FES and target FES connection details in file environmentMigration.properties file:
   _ESTUDIO_IMPORT_APPLICATION_LIST=EVENT_PROCESS4:1.0,EVENT_PROCESS5:2.0_ESTUDIO_IMPORT_SERVICES_LIST=Feeder:4.0,Display:4.0,JmsIn:5.0SOURCE_RMI_CONNECTION_STRING=rmi://192.168.1.76:2047TARGET_RMI_CONNECTION_STRING=rmi://localhost:2047 _ESTUDIO_TARGET_APPLICATION_LABEL=Production

2. Run command ant EnvironmentMigration in CLI_HOME/EnvironmetMigration. Refer the figure below for sample output.
   
   Image Modified
   Sample output for importing Applications from remote FES

...

1. Refer Configure Peer Server to Environment to configure the Environment to a peer server.
2. Export the required application from Testing Enterprise Server.
3. Copy the exported zip file to the local disk of the Production Enterprise Server machine.
4. Import the application to Production Enterprise Server.
5. Refer the Change Environment Of the Event Process From CLI to change the Environment to Production also deploys components into fpsProd

...

1. In the above SIMPLECHAT_1.0.zip exported, all the components are deployed in peer 'fps' by default, to deploy that peer to 'mypeer' when imported.
2. Create a file with any name, for example, 'replace.properties' with content: <string to be replaced>=<replacement string>. In this example, content is: fps=mypeer
3. Set the properties for necessary options such as input zipfile, output zip file and properties in eStudio.properties file:
   _ESTUDIO_INPUT_ZIP_FILE=/temp/import/SIMPLECHAT_1.0.zip_ESTUDIO_OUTPUT_ZIP_FILE=/temp/import/SIMPLECHAT_1.0_MYPEER.zip_ESTUDIO_PROPERTIES_FILE_ZIP=/temp/import/replace.properties
4. Run command "ant replaceInZip" in CLI_HOME. Refer the below figure for sample output.

Image Modified