Wednesday, July 2, 2014

Checklist for succesfull installation of CORDYS BOP

Introduction

In this page is explained how-to check if the installation of Cordys is succesfull and ready to use. The tests preformed are a basic indication if the functionality is working as expected and does not guaranty that you won't run into problems.

Cars checkup

  • After the installation check in the logs directory the following file for errors: <CARS_INSTALL_DIR>/install_log/Cordys_Admin_Repository_Server_x.x_InstallLog.log
    • Check in the section "Summary" if there are 0 Warnings/NonFatalErrors/FatalError.
  • Check if the configuration file of CARS is created and if it contains the proper values as selected during the installation: <CARS_INSTALL_DIR>/bin (sbin)/slapd.conf
    • The file should contain the proper value for "Suffix". This suffix should also be mentioned at the end of the "Rootdn". Also check when "SSL" is selected if the last 3 lines have the following structure: TLS<XXXXX>File " <CARS_INSTALL_DIR>/certificates/<FQDN>-xxxx.xxx"
  • Make a connection to the port as configured during the installation. This can be done by opening a terminal/command prompt and issue the following command:
    • telnet <HOSTNAME> 6366
      If the server respons is:  Connected than the ldap server is running. To exit press <CTRL>] -> quit

Cordys checkup

  • After the installation of the baseline check in the logs directory the following file for errors (Please mind that the file will only be created when the installer is closed by selecting "finish"in the baseline installer): <CORDYS_INSTALL_DIR>install_log/Cordys BOP-4 installation.log
    • Check in the section "Summary" if there are 0 Warnings/NonFatalErrors/FatalError.
  • After the installation of the ISV packages (applications) check if the screen is only showing green flags. If this is the case the installation of the ISV packages is succesfull. When there are orange triangels, click on it and follow the instructions. When the tasks are completed the installation is successful.
  • Log into Cordys, with the web browser  IE8, for the first time with the user that preformed the installation. See if the Cordys CUSP is loaded.
    • Open the System Resource Manager. Make sure all the service containers with the startup-type automatic are started. If this is not the case start them. (Right mouse click --> start).
    • Open the Application Registry. Check if the ISV Packages (applications) have been loaded on the server.
  • Create a user (if you use Integrated Domain Authentication, make sure the "Login ID" corresponds to the operating system/domain account).
    • Open the User Manager. Click on the plus button, select the Authentication Type and fill in the user details. Click on the save button.
    • Assign the following roles to the new user: Deployer and Developer.
  • Open a new browser and log in to Cordys as the just created user.
    • Open the Workspace Documents. Create a new workspace by clicking on the plus button.
    • Click on the 'here' button to create a new solution and project.
    • After creating the solution and project, right mouse click on the project and select new --> other. Select Business Process Model.
    • Create a simple flow (start -- activity -- end). Save the business process model, validate and generate bpml (F9) and run the model (F12).
    • Open the Process Instance Manager. Check if the Process Name is mentioned in the table and if the process has the status complete.
All above actions should be completed without errors.

Cordys BAM checkup

  • After the installation of the Cordys BAM MDM Model isvp check if the MDM model has been published successfully.
    • Open the MDM Model browser and check if the Runtime Model BAM is published.
    • Open the BAM Administration. Check if there is a process selected in the table and click on the upload button. Click no and check if the status is completed.
Hope it helps...!!!!

Thanks & Regards,
Madhusudan Reddy K

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home