Replicate IBM Tivoli LDAP Server - ldap

We had an environment with two IBM Tivoli LDAP servers with IBM Tivoli LDAP configured in peer to peer mode also utilizing NLB.
One our machines crashed and we installed a fresh OS on the machine with empty IBM Tivoli LDAP server.
Now we want to replicate working Tivoli LDAP server to this new server. Can somebody please tell us how can we configure this peer-to=peer replication again with old and new LDAP server without losing any data?

You can either export a ldif file and import it to the new server or use a Tivoli Directory Server (TDI) to move data between the servers. TDI can also be used afterwards to keep the two directory servers in sync.

Related

Protocols for MSSQLSERVER Not Visible in SQL Server Configuration Manager

I am trying to make a remote connection to a SQL Server database and have been having problems. When trying to connect it keeps timing out.
I have consulted the following post:
Services not visible in SQL Server Configuration Manager
I have taken steps outlined in the following questions:
Which IP to Use to Remote Connect to SQL Server?
Connect to SQL Server from Web App
https://networkengineering.stackexchange.com/questions/46599/how-to-remote-connect-to-sql-server?noredirect=1#comment78624_46599
https://dba.stackexchange.com/questions/193975/how-to-expose-sql-server-hosted-on-intranet-to-connect-remotely?noredirect=1#comment377827_193975
At this point I think I am being blocked by a hardware firewall, or that I don't have all the proper modules installed on the SQL Server.
When looking at online tutorials such as this: https://www.habaneroconsulting.com/stories/insights/2015/tcpip-is-disabled-by-default-in-microsoft-sql-server-2014
It seems that Protocols for MSSQLSERVER should be visible from this dropdown.
I have tried installing all the SQL Server related packages from the Web Platform Installer.
SQLEXPRESS and SQLSERVER are two different software packages and must be installed separately.

How to configure two IBM MobileFirst Platform v7.1 server to one IBM http web server?

Please help me in configuring two IBM MObilefirst Platform 7.1 ap server to one IBM HTTP Web server. As per the IBM Documents I should follow Server Farm configurations.
Need guidance in doing the same.
Scenario 1
Resources: Two App Servers with IBM MobileFirst Platform v7.1 installed and plugin-cfg geneated using jConsole. Each app server is having separate DB for each. One web server with IBM HTTP installed.
Scenario 2Resources: Two App Servers with IBM MobileFirst Platform v7.1 installed and plugin-cfg geneated using jConsole. Both the app server is having common DB. One web server with IBM HTTP installed.
I need both the app servers to be up at the same time in the above given scenarios. Please let me know in scenario one should I install any separate plugin for setting up server farm configuration.
note:In Scenario 2 currently only one App server can be made up at a time
Use JConsole to generate the plugin-cfg.xml from your individual Liberty servers. You can either merge the plugin-cfg.xml files manually or use Job Manager to generate a merged plugin from both the Liberty servers.
More details here:
Setting up HTTP Server in a WebSphere Application Server Liberty profile farm
Manually merge the files by using a text editor.
Use the job manager to submit a Generate merged plugin configuration for Liberty servers job.
Generating a merged plug-in configuration for Liberty profile servers using the job manager

TFS Configuration Error

I am facing a problem that when i try to configure my TFS it show me the following Error Message
Error
TF255049: A connection cannot be made to the server that is running SQL Server. Verify that you have entered the correct name for the server, including the instance name, that the server you are attempting to connect to is online, and that you have the required permissions to connect. If you are attempting to connect to the remote SQL Server instance, then verify that it is configured to allow remote connections, that TCP/IP protocol is both enabled and configured to use port 1433 (default), and that Windows Firewall does not block this port.
Check whether the SQL version is supported by the TFS version: https://www.visualstudio.com/en-us/docs/setup-admin/requirements#sql-server
Check the permission of the account that you use, and make sure it belongs to SysAdmin Server Role.
As #Daniel mentioned in comment, follow the troubleshooting steps provided in the error message, and check this blog to see whether it is helpful: https://elhajj.wordpress.com/2013/02/25/workaround-error-tf255049-punching-a-hole-through-windows-firewall/
I was running an upgrade from TFS 2018 to Azure DevOps 2020.
After the server restart, the Azure DevOps Server Configuration wizard opened.
I was logged in as the local machine administrator and got this error (TF255049: A connection cannot be made to the server that is running SQL Server...) when trying to connect to my SQL Server machine (to chose the configuration database).
I logged in as Network Administrator, started the wizard again and the SQL connection worked.
To restart the Azure DevOps Configuration Wizard again...
Open the Azure DevOps Administration Console and choose Configure Installed Features to open the Server Configuration Wizard...

Why is MobileFirst Server Configuration Tool not letting me deploy with libertyAdminUser and libertyAdminPassword?

I'm trying to deploy a MobileFirst server to a local Liberty server configured with an LDAP server.
When I try and deploy my server configuration the admin task fails due to lack of attributes for connecting to Liberty.
BUILD FAILED
C:\Users\Administrator\Documents\IBM MobileFirst Platform Server Data\Server Configuration Tool\Configuration_Hello MobileFirst Server\Hello MobileFirst Server.xml:88: The element <installWorklightAdmin>, <jmx libertyAdminUser=".." libertyAdminPassword="..."/> is missing. A default user cannot be created for this server.
I have tried updating the server configuration file manually before deploying, but the server configuration tool is just saving over the changes.
How can I resolve this problem from within the Server Configuration Tool?
The Server Configuration Tool in MFP 7.0 can't be used to make an install on a Liberty server that is configured with LDAP.
In the simplified install process of the Server Configuration Tool, it automatically creates a Liberty Administrator in a basic registry and this is not possible if Liberty is configured with LDAP.
If you don't want to create ant files manually, you can:
Export the ant files that you created with the Server Configuration Tool (Menu File/Export Configuration as Ant files...)
Edit them so that they have the right attributes in the jmx element (you need to provide the login of password of a user that will be used as Liberty Administrator and that the apps will use to perform JMX calls)
Run the ant files as described here
For the admin: https://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.installconfig.doc/install_config/r_wlconsole_ant_tasks.html
For the runtime: https://www-01.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.deploy.doc/devref/c_project_war_file_ant_tasks.html
You may encrypt the password of the JMX user with the Liberty securityUtility program (in LibertyInstallDir/bin)

LDAP test environment

what's the best way to develop with ldap without having the connection to the productive ldap server. Can you recommend some software?
Thanks
I'd say a test instance of OpenLDAP :)
If you're more into the Microsoft space, you could also check out:
Active Directory Lightweight Directory Services (AD LDS)
which is a Windows service based subset of the full AD. You can spin up multiple instances of AD LDS and since it's a Windows service, you can also turn it off when no longer needed.
It depends on what kind of LDAP server you have in production. Usually it's a question "AD or not AD?"
If your productions server is AD then it would be either virtual machine with a domain controller or a local instance of AD LDS (formerly ADAM).
If your production server is a generic LDAP server then there is a wide set of options. These days I would use a virtual machine with any Linux and OpenLDAP or/and Fedora Directory Server, or a local instance(s) of ApacheDS or OpenDS.
If you do not want to install/host/configure a Microsoft Server with Active Directory, you can use the following for LDAP testing purposes:
https://documize.github.io/ad-ldap-test-server/
Try
https://github.com/Upekshe/simple-ldap-server
Its running a nodejs server, highly configurable, supports both ldap and ldaps
Dokerized version
https://hub.docker.com/r/upekshejay/simple-ldap-test-server