Installing CA Process Automation version 4.2

book

Article ID: 18806

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent CA Process Automation Base

Issue/Introduction

The following will guide you step by step through an installation of CA EEM 12.5.1 and CA Process Automation 4.2.

The scope for the document is a new install of both products in a Windows Server environment and a MS SQL Server database. This doc assumes that Java 7 JDK is already installed on this machine.


Additional information regarding upgrades, Linux, Oracle and MySQL can be found in the CA Process Automation installation guide.


EEM 12.5.1 install


Mount the ISO


Select the proper installer, 32 or 64 bit

Select your install language and click OK Figure 60

Select Next on the Introduction dialog


Accept the License Agreement and click Next


Select the location for the components and click Next



Leave the CA Directory information as the installer has it unless you have been directed by EEM Support or EEM Engineering specifically to modify the port and/or DB size. Click Next.


Enter the EiamAdmin password and click Next. You will need to remember this password.


Enable FIPS only if this is required by your company. If you don?t know, do not enable it. It can be enabled post install if it is required. Click Next.


Verify the information and click Install on the Pre-Installation Summary


The installer runs

This can take several minutes, then ends with the completion screen. Click Done.




When the installation has completed, from the server startmenu, select All Programs // CA // Embedded Entitlements Manager // Admin UI




This will open the browser to a certificate page - you need to select the link for "Continue to this website"



From here the CA EEM login page. Enter EiamAdmin for the user and the password for this user that you used during the installation, and click the Log In button. The Application drop down on this login page will only have the one "Global" application for a new installation. Once CA Process Automation is installed and registered to EEM, there will be an entry for CA Process Automation in the Application drop down as well.




If you successfully log in to EEM as EiamAdmin, then you have verified that CA EEM is functional and can continue with the CA Process Automation installation. If you are not able to log into CA EEM, do NOT continue with the CA Process Automation installation. Call CA Support for assistance.



NOTE: If you are unable to open a browser on the server where EEM was installed due to restrictions in your environment, then from any machine on your network open a browser and enter the URL http://{eem_server_name}:5250/spin/eiam

Installing CA Process Automation version 4.2

Mount both ISO files



From DVD 1 run the third party installer



Select your language and click OK



Click Next on the Welcome screen



Accept the License Agreement and click Next




Choose the installation directory and click Next




Click Next on the Prerequisites screen




JBoss is installed, this can take a few minutes



Then you will be presented with the JDBC Jars installation page.

Click on the ADD Files button near the bottom of the dialog screen. That will change the screen to present a drop down where you select the Database type that will be used for CA Process Automation.

Once the DB Type is selected, the jar file location will be filled out if you are using either MSSQL Server or Oracle.

If you are using the MySQL database, you will need to provide the path to the JDBC Jar file using the Browse button, which are included in the installation DVD. 

By default for MSSQL Server, CA Process Automation now distributes and uses the open source jTDS driver.

Select your Database Type, provide the JDBC Jar if necessary, and click Next




Click Next on the Prerequisites completion screen



Provide the location of DVD2 and click Finish

The installer begins copying files, which could take a little while




The dialog box may even disappear for a minute or two.

You will then be presented with the Welcome screen, click Next




Accept the License Agreement and click Next

Since the Java 7 JDK was installed prior to running the CA Process Automation installation, the location of the JDK install directory should automatically be picked up by the installer. If however the installer does not automatically detect the install location of the JDK, browse to that directory then click Next. This MUST be a JDK (Java Development Kit) installation, and not just the JRE (Java Runtime Environment) installation



The installer begins copying configuration files

You are then presented with the first configuration screen. Here you would select to allow secure (SSL) communication, SiteMinder integration and Load Balancer configuration.

For the purposes of this document, none of these will be selected as this is a basic installation walkthrough. Further information on configuring SSL, SiteMinder or a Load Balancer can be found in the CA Process Automation Installation guide.

Click Next




Enter your company name and click Next

On the certificate password screen is where you enter a password that will be used for controlling access to keys used for encrypted passwords and data.

This password is required when installing any other Orchestrators or cluster nodes to existing Orchestrators.

If you forget this password, you will be required to rerun this installation process again to reset this password.

Please keep a record of the CA Process Automation certificate password and click Next

Select your options for shortcuts and click Next

On the General Properties dialog, there are 3 sections

  • Server Host by default this is filled in with the server FQDN and should remain as FQDN
  • Display Name The default will match the "Server Host" field, but does not have to
  •          Support Secure Communication If on the first configuration screen you selected to Support Secure Communication, this should now be selected
  • Server Port This is the JBoss web server port. The default is 80 because JBoss is a Web Application Server and communicates on port 80 like any other web server. If you have another web server running on this server; IIS for example; then if you do not change this port number you will get an error message about the port being in use. You would need to change this to another open port such as 81. 
  • The port may also be in use by something like SQL Server Reporting Services -- go into Services.msc and stop the service to open up port 80. Verify port 80 is not in use in command line by typing "netstat -nao | find ":80". 



HTTP Port This is the port that CA Process Automation is accessed with. CA Process Automation is a deployed Java application, deployed to the JBoss web application server. The default port is 8080

HTTPS Port This is the secure port for CA Process Automation, the default is 8443

         Install as Windows Service Leave this selected to install the service for the Windows services control

JNDI Port Internal port only for Java naming service, default 1099

RMI Port Internal RMI port for the web server, default 1098

SNMP Port Trap listener port for PAM, default 162

Click Next




Set the temporary directory and click Next

The default location is usually alright, however depending on how you are logged on to the server where you are installing PAM, you may need to grant permissions on this folder, or select another folder

Enable Powershell execution and click Next. The path is automatically detected by the installer. If you do not wish to enable this at the time of installation, it can be enabled post installation

The EEM Settings dialog

Use FIPS-Compliant Certificate ONLY if when you installed EEM you selected Enable FIPS 140-2 Compatibility. If you did NOT select this for EEM, do NOT select it here

EEM Server This is the servername where you installed EEM. If you are installing PAM on the same server where you installed EEM please enter the actual servername and NOT the word localhost

EEM Application Name This is the application name that will be displayed in the drop down Application list on the EEM login screen, as well as used in communication between PAM and EEM. The default is "Process Automation", but this can be changed if you prefer

EEM Certificate File

Certificate Key File

The above two fields are NOT greyed out unless you select "Register Application with CA EEM". For a new installation of PAM you need to select the "Register" check box as shown.

If this is an upgrade of PAM, these fields would be filled out already, but you still want to select to Register the application (using the same application name from the previous install)for an upgrade due to possible changes in the access policies in EEM for CA Process Automation

EEM Certificate Password This is a password that is used for communication between Pam and EEM. It is not something that you will be prompted for again, but a good idea to keep somewhere. PLEASE NOTE - this is NOT the same as the Certificate Password from the previous Certificate Password dialog. This is completely different

Default Active Directory Domain This is ONLY used if EEM is connected to Acitve Directory AND configured for the Multiple AD Domain setup. If you enter anything here and you do not have the Active Directory Mutliple Domain setup configured in EEM, you will be able to log in to CA Process Automation a first time, however subsequent login attempts will all fail.

Enable NTLM Pass-Through Authentication Do not select this when first setting up PAM. This function is also used with Active Directory configured in EEM, but Support suggests strongly that you wait until after you have installed and verified the PAM installation to enable this. There is a simple change in the Oasisconfig.properties file (C:\Program Files\CA\PAM\server\c2o\.config) that can be done after the installation has been verified. Change "ntlm.enabled=false" to "ntlm.enabled=true" and recycle the Orchestrator Service.




Make sure Register Application with CA EEM is selected then click the Register button




Enter the EiamAdmin username and password and click OK

It may take a few minutes, then the success dialog will appear. Click OK


Back on the EEM configuration screen, you will see that the certificate file field has been filled out. Select the Test EEM Settings button.



You will be prompted with a warning, click OK

Type in pamadmin for both the username and password and click OK

The following should then display with the values OK OK and YES

If you do NOT see OK OK YES do NOT proceed and call CA Support

Otherwise click OK



You will be returned to the Embedded Entitlements Manager (EEM) Security Settings screen once again where you will select Next




On the database settings screen select the Database type using the drop down.

Fields are auto-populated, fill in the Password and update other fields if necessary then click on Create Database.

If Username/password are not working, verify/update credentials in SQL Server Management Studio. Also ensure that the instance is using "Mixed Mode" for authentication in the instance properties in SSMS. 




If unsuccessful, a pop up will appear. Click OK and verify the settings with your DBA

If successful, a success pop up will appear, click OK


On this first Database settings dialog then click Next

On the following Runtime Database settings dialog, put a check in the copy from main repository at the top. This will automatically fill in the fields below with the information from the previous dialog




For Runtime Database IF you change the name here (this can be different from the repository database from the previous dialog) then you must click on the Create Database button again. If you do NOT change the name just click on the Next button

On the following Reporting Database dialog, again put a check in the copy from main repository at the top and if you change the name for Reporting Database then click on the Create Database button. Otherwise, click Next




* It is recommended that you keep the three (repository, runtime, reporting) databases separate, but not required.

On the Additional Jars screen, it is recommended that you select the boxes for the jar file for future installs (agents, etc) and monitoring. Click Next




The installer, initializes, copies and begins the install. This could take a while depending on your server resources

Once it has completed you will get the following screen, click Finish to exit the installer dialog

Open the Windows Services control panel and start the CA Process Automation Orchestrator Service. It is set to Automatic, but does not start up after the initial installation.



At this point the tables are built in the database so it could take up to 10 minutes or more for the application to be ready to be accessed the first time.

Open a browser and enter the URL

http://{pam_server_name}:8080/itpam

You can also do this by going to Start // All Programs // CA // CA Process Automation 4.2 // Start CA Process Automation




You will be presented with the CA Process Automation login screen. Enter the username and password of "pamadmin" - no quotes, same for both user and password





Environment

Release: ITPASA99000-4.3-Process Automation-Add On License for-CA Server Automation
Component:

Resolution

     You will be presented with the CA Process Automation login screen. Enter the username and password of "pamadmin" - no quotes, same for both user and password


Attachments