Unica Administrator

Role: Unica Administrator
Location: Remote

Top 3 skills:
1.Unica campaign, platform and plan installation and upgrade
2.JBOSS and DB2
3.RHEL Servers


Job Description/ Responsibilities:
1. Core Technical Skills
The upgrade is not just a "click-next" installer; it involves manual database manipulation and application server re-configuration.
• Database Administration (SQL Server, Oracle, DB2, or MariaDB):
o SQL Proficiency: You must run manual SQL upgrade scripts (e.g., ManagerSchema_251_DB_Type_upg.sql) to bridge the gaps between schema versions.
o Backup & Recovery: Proficiency in performing full schema exports/backups before each hop in the upgrade path.
o Permissions: Knowledge of granting CREATE, DROP, and ALTER permissions required specifically for the upgrade phase.
• Web Application Server Management (WAS, WebLogic, Tomcat, JBoss):
o Ability to undeploy/redeploy WAR/EAR files.
o Knowledge of JVM arguments and memory settings (Unica 25.1 may have higher memory requirements than 12.1).
o Experience configuring Data Sources (JDBC) and connection pools.
• Operating System Mastery (RHEL/Linux or Windows Server):
o Linux/Unix: Comfort with command-line utilities, shell scripting, and file permissions (chmod, chown).
o Environment Variables: Ability to manage JAVA_HOME, UNICA_HOME, and library paths (like LD_LIBRARY_PATH).

2. Unica-Specific Product Knowledge
• Upgrade Methodologies:
o In-Place Upgrade: Installing 25.1 over the 12.1 directory (requires interim hops like 12.1.10).
o Fast Upgrade: A newer HCL method that allows moving from 12.1.x directly to 25.1.0.1 using a specialized migration tool to minimize downtime.
• Configuration Tools: Proficiency with the configTool utility to import/export metadata and properties between versions.
• Product Interdependencies: Understanding that Unica Platform must always be upgraded first before Campaign, Plan, or Journey.
• Component Migration: Knowledge of migrating specific components like Campaign Flowcharts (.ses files) and Catalogs, ensuring they remain compatible with the new 25.1 UI.

3. The "Upgrade Path" Knowledge
You must understand the versioning logic. Version 25.1 (released in 2025/2026) is the successor to the 12.x branch.
• Hop 1: Upgrade 12.1.0 to 12.1.10 (the "bridge" version).
• Hop 2: Upgrade 12.1.10 to 25.1.0.
• Hop 3: Apply the latest fix pack (e.g., 25.1.0.1).

4. Security & Compliance
• SSL/TLS Certificates: Knowledge of OpenSSL to generate new certificates, as older GSKIT-based configurations from 12.1 might need updating to modern standards in 25.1.
• Authentication: Experience with LDAP/Active Directory integration if your Unica instance uses external identity providers

Additional Information:
1. Point of contact from delivery stand point
2. Manage the client communication, internal and external teams
3. Drive the platform upgrade from 12.1.6 to 25.1 in 4 environments supporting End to end testing without impacting project timelines.
4. Provide weekly status to client