I would like to know the steps involved in migrating the Oracle Iplanet webserver(v6) to WAS Liberty profile. Also please let me know the feasibility and the challenges involved.
The changes needed will depend on the application being migrated. You can use the binary scanner tool to scan your application for changes needed to migrate to liberty. Run the tool against your war/ear/jar file(s) with the --sourceAppServer=other --targetAppServer=liberty options.
Related
We have a mobile apps running on v7.1. And now we want to migrate to v8.0. I have read the migration cookbook, however it does not seem to explain the following:
How to migrate the existing user? The user has already subscribe to push-notification. I believe the information are stored in mobile first database, and I read from this it does not have a script to migrate the database.
How do we keep the existing user information? So, the migration process will require 2 versions running in parallel and slowly move the user to the new version? It seems that we cannot “upgrade” the old server to the new version, is that correct?
You cannot migrate the user information from MFP 7.x to 8.0 as the security architecture is completely different between these versions.
I am trying to migrate reports from BOBJ 4.1 SP5 Patch 3 from Development to Production using Upgrade management tool.
However after the upgrade is completed, I see that no security for folders or reports is migrated. Is there anything I need to select or the Upgrade management cannot migrate security.
Best way to "migrate" (publish I said) is Central Management Console > Promotion Management. With this option you can choose whatever you select (folders, access levels, universes, connections...)
Is this what you were looking for?
Best regards
I would like to migrate a portal which is developed in WebSphere content management system into OpenCms (Content management system). To implement this I want to import the WebSphere template files into OpenCms, I have done R&D for it but I didn't find any solution. Can any one please guide me how to do it?
I don't believe there is any provided solution for that. So you will either need to build your own migration tool, create it from scratch in opencms or stick with WebSphere Portal.
I'm quite a newbie, just trying to learn some new things. I've recently started learning c# etc and I'd also like to create a new SQL Server database using SQL Server Management Studio.
The thing is that for some reason I am not able to connect to the server. I might have done something wrong (or haven't done something that I should have done). Been researching the problem a lot on google and I found some tips but I still can't make it work.
I even found some installation tutorial in here: http://www.sqlcoffee.com/SQLServer2014_0005.htm and I only noticed that I used some different options (I used default, didn't change anything) like for example in "Database Engine Config" I chose "Windows authentication mode".
So that's what I get: http://imgur.com/2ftOdSB
Also I think I may have some problem with services, because when I go to the server configuration manager, the list is completely empty.
Thanks for any tips. If I don't solve this, I can always uninstall SQL Server Management Studio and reinstall it - this time following the steps in the tutorial. Hopefully that wont be necessary so help me please:)!
I've had a look at the link you posted about the installation instructions. As I mentioned before SQL server enterprise (database engine) won't install on a non-Server OS, You'll need at least Windows Server 2008. Have a look at msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx for the system requirements. During the installation there must have been an option to install the database engine, but it was probably disabled because of your OS.
I suggest you uninstall 2014 Enterprise and download SQL Server 2014 express microsoft.com/en-gb/download/details.aspx?id=42299 and make sure you select database engine as part of the installation.
If you want to get into SQL, I would suggest trying out MySQL first. I've utilized it a little bit and found it to be fairly simple with a decent amount of documentation. This version of SQL will still function with various languages. It doesn't utilize Windows authentication, but rather lets you set a root password specific to the database itself. I don't know if your software is similar to that but there may be an option to not use Windows authentication and instead authenticate within the database software itself.
I've been following Microsoft's guide for installing a dev environment on Windows 7:
http://msdn.microsoft.com/en-us/library/ee554869.aspx
In order for it to not run like a dog I've created a SQL Server 2008 instance on our database server specifically for this dev machine. The article does mention that you might be wanting to use an external database in regard to making sure the database cumulative update is installed. It doesn't make any other mention of configuring it to use a external database. I was hoping that the configuration wizard would then prompt about which database to use but annoyingly it just set-up the configuration database locally.
How do I go about installing SharePoint on a dev environment with an external database, and will I need to reformat this machine and do it all again?
Well, this depends on what your environment looks like. For instance, is this machine part of a domain?
If so, it should be as simple as selecting "Server Farm Install", or something like that when you did the binaries installation. Then, when you run Products and Configuration Wizard, it will ask you for DB info. Note: if you are doing this, I would recommend you to be part of the 'sa' role on the database server as you will be creating databases.
If you are not part of a domain, it gets a little trickier, but not too bad. Check out this article.
http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=112
-= Plan B =-
You can always give this a whirl. This is the method we use to keep the DB guys from screaming. It also allows us to give our databases nice names.
http://technet.microsoft.com/en-us/library/cc262869.aspx