Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. How to Implement PowerCenter on Microsoft Azure

How to Implement PowerCenter on Microsoft Azure

How to Implement PowerCenter on Microsoft Azure

Step 7. Create Informatica Services in the Azure Cloud

Step 7. Create Informatica Services in the Azure Cloud

You can restore and update Informatica services, such as the PowerCenter Repository Service and the Integration Service in the Azure cloud.
  1. Start the Informatica domain.
    Enter the infaservice startup command in the following installer location:
    $INFA_HOME/tomcat/bin
  2. Add license with the following command in the command line:
    $INFA_HOME/isp/bin/infacmd addLicense -lf<absolutepath>/license.key -dn $domainName -un Administrator -pd Administrator -ln License_Name
  3. When you migrate PowerCenter from on-premises, restore the repository contents from the backup file with the
    pmrep restore
    command with the same repository name in the following format in the
    $INFA_HOME/server/bin/pmrep
    directory:
    pmrep restore [-u <domain_user_name>] [-s <domain_user_security_domain>] [-p <domain_password> | -P <domain_password_environment_variable>] -i <input_file_name> [-g (create global repository)] [-y (enable object versioning)] [-b (skip workflow and session logs)] [-j (skip deployment group history)] [-q (skip MX data)] [-f (skip task statistics)] [-a (as new repository)] [-e (exit if domain name in the binary file is different from current domain name)]
    For example,
    pmrep restore -u admin -p admin -i C:\license_check.rep
  4. Enter the
    infacmd isp UpdateRepositoryService
    command in the
    $INFA_HOME/isp/bin
    directory to update the PowerCenter Repository Service repository user and the repository database details as seen in the following format:
    infacmd isp updateRepositoryService <-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password [<-SecurityDomain|-sdn> security_domain] [<-Gateway|-hp> gateway_host1:port gateway_host2:port...] [<-ResilienceTimeout|-re> timeout_period_in_seconds] <-ServiceName|-sn> service_name [<-NodeName|-nn> node_name] [<-BackupNodes|-bn> node1 node2 ...] [<-ServiceOptions|-so> option_name=value ...(AllowWritesWithRACaching, CheckinCommentsRequired, CodePage, ConnectString, DBPassword, DBPoolExpiryThreshold, DBPoolExpiryTimeout, DBUser, DatabaseArrayOperationSize, DatabaseConnectionTimeout, DatabasePoolSize, DatabaseType, EnableRepAgentCaching, ErrorSeverityLevel, HeartBeatInterval, MaxResilienceTimeout, MaximumConnections, MaximumLocks, OperatingMode, OptimizeDatabaseSchema, PreserveMXData, RACacheCapacity, SecurityAuditTrail, ServiceResilienceTimeout, TableOwnerName, TablespaceName, TrustedConnection, useDSN, DataSourceName)]
    If you update the PowerCenter Repository Service with the same on-premise PowerCenter Integration Service properties, you do not need to update the PowerCenter Integration Service.
    To update the PowerCenter Integration Service, enter the infacmd isp UpdateIntegrationService command in the
    $INFA_HOME/isp/bin
    directory in the following format:
    infacmd isp UpdateIntegrationService <-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password [<-SecurityDomain|-sdn> security_domain] [<-Gateway|-hp> gateway_host1:port gateway_host2:port...] [<-ResilienceTimeout|-re> timeout_period_in_seconds] <-ServiceName|-sn> service_name [<-NodeName|-nn> node_name|<-GridName|-gn> grid_name] [<-BackupNodes|-bn> node1 node2 ...] [<-RepositoryService|-rs> repository_service_name] [<-RepositoryUser|-ru> repository_user] [<-RepositoryPassword|-rp> repository_password] [<-RepositoryUserSecurityDomain|-rsdn> repository_user_security_domain] [<-ServiceOptions|-so> option_name=value ...]

0 COMMENTS

We’d like to hear from you!