Yamuna M L’s Post

🔧✨ Why did the Configuration Management Database (CMDB) go to therapy? Because it had too many unresolved dependencies and needed help managing its relationships! 😂 Keeping track of configurations can be complex—Let's talk TODAY about making sure our CIs are happy and healthy! ☎ 📧 💻 https://lnkd.in/egaKc4NP

Hello every one , Please find the below requirement and please share suitable profiles to Kevin@aaur.tech DESCRIPTION: Other Industry External Names for Role: Tester, System Administrator, Database Administrator, IT Support Specialist. This job role performs IT services as testing, developing, administering, troubleshooting and supporting customer application systems. The IT Engineer is responsible for implementing the services requested by the customer with the agreed service level agreements in the frame contract. The IT Engineer is part of customer team and work in customer premises or remotely for the customer wherever possible TOOLS: - Deployment tools - Verification tools - Performance management and monitoring tools - Fault management tools - Trouble Ticket Management tools - Test management tool COMPETENCES: * Applying Expertise & Technology * Analyzing and problem-solving abilities * Delivering Results & Meeting Customer Expectations * Planning & Organizing * Following Instructions & Procedures RESPONSIBILITIES: * Administer an IT system. Installation /configuration of customer infrastructure with third-party supervision. Monitoring, optimization and tuning of the infrastructure installed. Dimensioning, Capacity planning, support the selection of products. * Writing technical documentation. * Test an IT system. Preparation and verification of System Integration and test environments. * Define test planning, defining test case dependencies and priorities to meet the required test execution coverage within the SLAs. * Executes tests, based on a Test Object List and a test Strategy specification. * Document test results in a Test Report. * Uses test reporting tools to document test specification and results. * Develop codes and interfaces on an IT system. * Debug and correct SW faults. * Support Service Assurance. Incident Management. Restoring normal service operation (within SLA limits) as quickly as possible while minimizing the impact on business operations. * Plan/design/development of scripts in order to monitor the business processes KPIs(volumes/performances). Analysis of business process KPIs and data quality outcomes, troubleshooting and designing/managing the relevant improvement or resolution processes or massive data realignment. * Plan/design/development of scripts/data needed for the execution of technical jobs (recursive/ one shot). Preparation of models for the estimation of volume growth and planning/design the future needs in terms of hardware and software licenses EXPERIENCE and QUALIFICATIONS: * Experience in technologies and customer systems or products to administrate. Knowledge on System Administration (OS, network, DBMS, …) * Experience on system process products to test and tools to use. Knowledge on software development process and automation test. * Infrastructure knowledge (OS, network, scripting …). Ability to identify and set KPI

We are looking for L3 Support Engineer for Payment Platform. No of positions – 8 nos Mode - Work from home. Work in shifts to ensure round-the-clock support coverage for the payment platform.   Job Description: The L3 Support Engineer for our Payment Platform (Online and POS) will be responsible for managing and resolving complex technical issues, ensuring the highest level of service reliability, and supporting the L3 lead in overseeing the platform's operations. Skills required: Should have minimum 5 to 7 years of experience in a similar role, with a strong background in payment systems, Java ecosystem, and team collaboration. Must be ready to work in shifts to provide 24/7 support coverage. Should have the capability of quick triaging and bug resolution. Technical Skills:  Strong knowledge of payment gateways, transaction processing, and financial systems. Proficiency in Java and related frameworks (Spring, Hibernate, etc.). Experience with microservices development (MACH framework). Expertise in quality engineering, triaging, and bug resolution. Proficiency in logging and observability analysis tools like Splunk and Dynatrace. AWS expertise. Experience with NOSQL databases (Document-based). Knowledge of in-memory caching technologies (e.g., Redis). Familiarity with event-driven architecture and technologies like Kafka. Proficiency with JIRA, Confluence, and ServiceNow. Knowledge of PMS/POS integration with Freedom Pay middleware (FCC client, FCC Listener). Knowledge of Credit Card Devices (Ingenico or similar). Knowledge of Point of Interaction Application Loader (PAL) packages/firmware. Knowledge of SSL Certificate renewals across Payment Integrations. Soft Skills Problem-Solving: Excellent analytical and problem-solving skills with a focus on root cause analysis and long-term solutions. Communication: Strong verbal and written communication skills, with the ability to explain complex technical issues to non-technical stakeholders. Availability: Willingness to work in shifts, including nights, weekends, and holidays, as needed. Key Responsibilities  Issue Resolution: Manage and resolve escalated technical issues related to the payment platform, ensuring timely and effective solutions.  System Monitoring: Monitor system performance, identify potential issues, and implement proactive measures to prevent downtime. Incident Management: Participate in incident response efforts, coordinate with cross-functional teams, and communicate effectively with stakeholders. Shift Work: Work in shifts to ensure round-the-clock support coverage for the payment platform. Collaboration: Work closely with development, QA, and product teams to ensure seamless integration and deployment of new features and updates. Compliance and Security: Ensure all activities comply with industry standards and regulations, maintaining the security and integrity of the payment platform. If you are interested, please share your CV on careers@ivavsys.com

Global certificate lifecycle management software market size is expected to reach $8.78 Bn by 2028 at a rate of 18.7%, segmented as by certificate type, secure sockets layer (ssl) or transport layer security (tls) certificates Read more https://lnkd.in/gm4u92V3 #marketresearch #marketreport

System Admin vs. System Engineer: What's the Difference? I often get asked about the difference between a system administrator (sysadmin) and a system engineer, and I thought it'd be fun to share my take on this since I have held both roles multiple times. At first glance, the roles might seem interchangeable, both deeply rooted in managing and optimizing IT infrastructures. However, the focus areas, responsibilities, and impact on business operations distinguish them significantly. System Administrators are the IT world's caretakers. They're responsible for maintaining and managing the daily operations of computer systems and networks. This includes tasks like setting up hardware, installing software, managing user accounts, ensuring security protocols are followed, and providing technical support. Sysadmins are the go-to people for keeping the lights on and ensuring that everything tech-related runs smoothly on a day-to-day basis. System Engineers, on the other hand, take a broader view. They are often involved in designing and implementing complex systems that meet an organization's business needs. This role requires a deep understanding of both hardware and software, as system engineers work on integrating systems to function together efficiently. They might be involved in system architecture, developing new technologies, and working on scalability to support growth. Essentially, they lay down the IT road map, focusing on the system's architecture and the future of the organization's technology landscape. To sum it up: While a sysadmin ensures that the current systems are running effectively, a system engineer designs and implements new systems or infrastructure improvements. Both roles are crucial; one maintains the stability and efficiency of day-to-day operations, and the other develops the vision and infrastructure that supports the organization's growth and evolving needs. Both positions require a strong foundation in IT and a deep understanding of the organization's technological framework. However, the system engineer's role is more about forward-thinking and planning, whereas the sysadmin's role is about maintaining and optimizing what currently exists. Whether you're a system administrator keeping our digital world running smoothly or a system engineer designing the IT landscapes of the future, your work is foundational to the success of every tech-reliant organization today.

Title:  Network Node Manager I (NNMi) Documentation Specialist Experience: 12+ Years Location: Onsite Houston, TX Job Type: W2/C2C   Job Summary: Utility Client is seeking a skilled Network Node Manager I (NNMi) Documentation Specialist to lead a critical documentation project with experience in utility industry or with large-scale IT environments. The successful candidate will be responsible for thoroughly documenting the architecture and application requirements of NNMi, an OpenText product, to ensure the system's continued functionality during future upgrades. This role requires a combination of technical expertise in NNMi and strong documentation skills. Key Responsibilities: Architecture Documentation: Collaborate with system architects and infrastructure engineers to create detailed architecture diagrams of the current NNMi environment. Ensure the architecture diagram accurately reflects the integration of NNMi within the existing IT infrastructure. Application Requirements Documentation: Work closely with NNMi Subject Matter Experts (SMEs) to document all conditions monitored by NNMi and the specific alerts configured within the application. Detail the functional requirements and decision logic used by NNMi to trigger alerts. Ensure comprehensive documentation of the current system's functionalities to facilitate future upgrades. Collaboration and Communication: Engage with various stakeholders, including IT, Network Operations, and Management, to gather necessary information and validate documentation. Provide regular updates to project managers and ensure alignment with project goals. Quality Assurance: Review and validate documentation to ensure accuracy, clarity, and completeness. Support the development of test cases and procedures based on documented requirements.   Project Scope: The primary objectives of this effort are to provide documentation for: Architecture diagram Application Requirements (Document all conditions that the application monitors / alerts) Deliverables: The document should provide the following: An architecture diagram Requirements document those documents each ‘decision’ or ‘function’ that is checked for an alert. Basically, this is a thorough documentation of what the software does. Please Respond to pGundraju@encloudservices.com

Hallo zusammen, I'm #hiring for a new Administrator (m/w/d) Exchange Umgebung, sowie Rückbau Domino position. Apply today or contact vijeta.priyam@trans4mation-bs.cz for more information. https://lnkd.in/dJEQJ2JW #msexchange #domino #msoutlook #incidentmanagement #changemanagement #documentation #problemmanagement #itservicemanagement #HCLnotes #german #itil #isoiec27000 #VMware #systemadministration #jira #2ndlevelsupport #itarchitecture

10 Troubleshooting Techniques Every Application Support Engineer Should Master In the dynamic world of technology, Technical Support Engineers play a critical role in ensuring that customers have a seamless experience with the products and services they use. A major part of their job involves troubleshooting, which is the process of identifying and resolving technical issues. Here are essential troubleshooting techniques every Application Support Engineer should master to diagnose and resolve issues efficiently: 1. Understanding the Application Environment Know the application’s architecture, environment configurations, and dependencies. 2. Issue Replication Verify and reproduce issues as reported to understand their scope. 3. Log Analysis Find specific errors, warnings, or unusual behaviors recorded during the application's operation. 4. Root Cause Analysis (RCA) Identify the true cause of an issue to avoid temporary fixes. 5. System Monitoring and Health Checks Track application health and catch anomalies early. 6. Network Troubleshooting Diagnose and resolve connectivity and latency issues. 7. Database Query and Performance Troubleshooting Address slow database queries and optimize database performance. 8. Dependency and Version Management Prevent conflicts due to incompatible dependencies or incorrect versions. 9. Stress and Load Testing Ensure the application performs well under heavy load. 10. Effective Communication and Documentation Document findings and communicate effectively with stakeholders. Mastering these techniques will make troubleshooting more systematic and reliable, leading to quicker resolutions and more robust application performance.

Hi All, Looking candidate for below role with one of our #BFSI client. Need local candidates. Open for W2 / C2C. Please share resume at vijay.pothiwal@tekfortune.com Job Title: ITAM & EOL Target State & Implementation Lead Duration: 6+ Months Contract Location: New York, NY (hybrid onsite) Job Description: Lead ITAM and EOL target definitions & gap assessments. Develop ITAM and EOL Procedures (including how obsolescence will be defined / managed, reconciliation process, asset, onboarding, dependency with procurement procedures, documentation of tool use, FFIEC/Client compliant) Define Target State for scanning solution, inventory target, attributes by asset type (and add asset types missing) Define EOL Target solution / source and documentation of EOL data source/ sustainability, by asset type - Define ITAM and EOL Governance to manage IT assets approaching EOL Develop ITAM and EOL Procedures V2, FFIEC/Client compliant, including: ·        How obsolescence will be defined / managed ·        Reconciliation process, ·        Asset, onboarding ·        Dependency with procurement procedures ·        Documentation of tools use Define Target State for CMDB: scanning solution, inventory target, attributes by asset type, data flows. Define reconciliation processes for ITAM vs discovery scan. Define EOL Target solution / golden source and documentation of EOL data source/ sustainability, by asset type. Define and implement appropriate governance to identify, track and report on ITAM and EOL Program, inclusive of preparing relevant material. Design oversight mechanisms for Senior Management to track ITAM and EOL (risk-based / TRM) Build governance to manage evidence (reconciliation reports, data source being used, remediation project and associated decommission/upgrade screenshots) and their approval to ensure audit trail for regulatory requests. Identify and qualify LoD1 ITAM/EOL risks as it pertains to accuracy and completeness of the asset inventory; finalize risk rating with relevant LoD1 stakeholders. Operationalize and execute LoD1 ITAM/EOL controls on a periodic basis. Log IT asset exclusions, risk acceptance, exceptions and remediation plans for audit and tracking. Identification, gathering, correlations of needed data inputs to calculate ITAM/EOL KPIs and KRIs, as co-constructed between LoD1 / LoD2 Validation of data quality for data points used for calculation and submission to LoD2. Create dashboard and update on a periodic basis. #ITAM #C2C #W2 #EOLtarget