Where Can I Download the Summer 18 version of the Salesforce Migration Tool? - migration

I am trying to download the latest version of the force.com migration tool (sometimes called the ANT migration tool.)
The download page seems to link to the Summer 2016 version of the tool (see errors below), despite claiming to link to the Summer 2018 version.
When I configure package.xml and run the .jar like so:
ant retrieveUnpackaged -lib path/to/ant-salesforce.jar
I get errors like this:
[sf:retrieve] package.xml - API version Summer '16 does not have access to Lightning Pages of type CommObjectPage
Note that this error message is not referring to the API version in the retrieve source sandbox. The sandbox API version is Winter '19.
I've been looking for a while now and still haven't found an alternative download link that correctly points at the Summer 2018 migration tool. Can anyone help?

Based on the error message, it sounds like the error message is complaining about the version number indicated in the retrieve package manifest, rather than the version of the migration tool.
If you go in the file named package.xml, there should be a tag <version>37.0</version>. If you change the number to anything 38.0 or higher, I would think the retrieve call should work for you.

Related

Cognos Data Manager to Cognos Datastage Migration

I'm looking at a migration project to migrate a client from Datamanager to Datastage. I can see that IBM have helpfully added in the Migration Assistant tool, but less helpfully, I cannot find any details on how to actually use it.
I did use it some years ago, and I'm aware that you need to do it in a command line interface and it works by taking an extract file and creating a Datastage job out of it, which is then reinstalled. However I haven't got my notes any more from that process.
If there is a user guide out there for this tool, I'd love to see it.
Cheers
JK
Your starting point would be the IBM support page and then see "How to download the tool" and ensure you have the required version (10.2.1 + Fix Pack 13 + Interim Fix) installed. The user guide PDF is part of the install in the sub-folder "datamanager/migration".

Publish Elm19 package, which first version was published as 18 package at a time Elm19 was already out

Some time after the release of Elm19 I published a library, which I needed for an Elm18 code base: thought2/elm-wikimedia-commons.
This worked well, it's listed in the community driven Elm18 package database: https://dmy.github.io/elm-0.18-packages/, can be installed and all good. Except the fact that the documentation is not shown in the package details, but that I heard is a known bug there. (But still I think this is very bad)
But the main problem is now, how to migrate the library to Elm 19: The actual migration steps are done and live in the master branch of the repo: http://github.com/thought2/elm-wikimedia-commons
The Elm18 versions proceeded to 1.1.0 in the meanwhile and after the migration there had to be done an API change, so I'd assume the latest version to become 2.0.0. If I add this to elm.json, the command elm publish tells me that this would be the first version and I should change this. Which is not right.
After a bit of research, I found out that the package (among other 18 ones that have been published in the same time period) is not listed in this json: https://package.elm-lang.org/all-packages This should contain all packages regardless of versions.
Any ideas what to do? This is really blocking my development, as I'm stuck in both lands now: 18 and 19. Would appreciate a lot if someone has some hints or solutions for me!
You shouldn't need to mess with the version number specified in elm.json.
If you set it back to the version of the package that is already published and run elm bump the elm program will look at the changes you've made to the package's API and set the new version accordingly.
Looking at https://github.com/thought2/elm-wikimedia-commons it doesn't look like any of your upgrade changes were breaking changes to your package API so the version won't be a 2.x.x, it will be a 1.x.x.
You'll need to remove the 2.0.0 git tag as well and instead add a tag for the version that elm bump tells you that your package is.

GlassFish 4.1.2 updatetool/pkg tools fail - missing pkg-bootstrap

Summary: The pkg-bootstrap.jar and related files are missing from the latest GlassFish 4.1.2 and this prevents the updatetool from running. What is the proper way to install and run updatetool on Windows 10?
Detail: I was working with the Java EE 7 tutorial and downloaded the Java EE 7 SDK Update 3 (not Web Profile) which is based on GlassFish Open Source Edition 4.1.2. I ran into a problem running the updatetool on Windows 10. When run, it gives the option to install itself but the installation fails. It looks like the update tool uses the pkg tool, and that uses a pkg-bootstrap to install itself the first time. However, this is no longer included in GlassFish 4.1.2. When the updatetool is run, it produces the following errors:
C:\glassfish4\bin>updatetool
The software needed for this command (updatetool) is not installed.
If you choose to install Update Tool, your system will be automatically
configured to periodically check for software updates. If you would like
to configure the tool to not check for updates, you can override the
default behavior via the tool's Preferences facility.
When this tool interacts with package repositories, some system information
such as your system's IP address and operating system type and version
is sent to the repository server. For more information please see:
http://wikis.oracle.com/display/updatecenter/UsageMetricsUC2
Once installation is complete you may re-run this command.
Would you like to install Update Tool now (y/n): y
C:\glassfish4>"C:\Program Files\Java\jdk1.8.0_121\bin\java" -Dimage.path="C:\glassfish4\bin\\.." -jar "C:\glassfish4\bin\\..\pkg/lib/pkg-client.jar" refresh
Error: Unable to access jarfile C:\glassfish4\bin\\..\pkg/lib/pkg-client.jar
C:\glassfish4>"C:\Program Files\Java\jdk1.8.0_121\bin\java" -Dimage.path="C:\glassfish4\bin\\.." -jar "C:\glassfish4\bin\\..\pkg/lib/pkg-bootstrap.jar" "C:\Users\[userid]\AppData\Local\Temp\pkg-bootstrap21687.props"
Error: Unable to access jarfile C:\glassfish4\bin\\..\pkg/lib/pkg-bootstrap.jar
C:\glassfish4\bin\pkg does not exist in either the latest Java EE 7 SDK Update 3 or the latest GlassFish 4.1.2. Some research on the nightly builds shows that the directory trees glassfish4/.org.opensolaris,pkg and glassfish4/pkg were removed between builds glassfish-4.1.2-b03-02_25_2017 and glassfish-4.1.2-b03-03_07_2017. I can't find anything that explains why they were removed or an alternate way to install the updatetool. My work around was to copy the two trees from glassfish-4.1.2-b03-02_25_2017 into c:\glassfish4 (from the Java EE 7 SDK Update 3) and that seems to work. But, I figure that if this was removed, there was a good reason for it, and I shouldn't be hacking it.
If there was a separate installation step for the package tool, I missed it. What is the proper way to get the updatetool to run on GlassFish 4.1.2?
I have jdk1.8.0_121 and jre1.8.0_121.
Thanks for your help.
I had the same problem as DevDevDev.
I went to the link in his post:
http://download.oracle.com/glassfish/4.1.2/nightly/index.html
Downloaded the archive:
glassfish-4.1.2-b03-02_25_2017
http://download.oracle.com/glassfish/4.1.2/nightly/glassfish-4.1.2-b03-02_25_2017.zip
Extracted the missing folders into my glassfish directory:
/glassfish4/pkg
/glassfish4/.org.opensolaris,pkg
As DevDevDev I have questions about why it was removed but it works for me...for now.... Hope it helps someone else. Thank you DevDevDev I would not have solved this without your post!
I was working with Java SE. Then I needed to work with JAX-WS, so I went into the same website as you.
Basically, it says that you have to:
Download the package (a compressed file with a folder called glassfish4)
Unzip the downloaded file (does not specify where)
voilá
It did not work for me, so I kept searching and I found this: https://forums.netbeans.org/post-91328.html
You just need to download this update from netbeans plugin Manager:
"Java EE Base"
Good luck!
I got the same problem too. It seems that glassfish 4.1 did not integrate the Update Tool, so as doc of oracle suggests, we'd better install SDK 6(glassfish 3). Here is Java EE 6 SDK Update 3, note that the version provided here is with JDK 7. If you already installed JDK in your windows 10, you may ignore it.
When you finish downloading the .exe file, you should not install SDK by double-click the .exe file. Instead, you should run below command:
java_ee_sdk-6u3-jdk7-windows-x64.exe -j [JRE-Home]
note, command here is the name of your .exe file and it needs console arg of JRE Home, mine command is as below:
java_ee_sdk-6u3-jdk7-windows-x64.exe -j D:\JDK\jre
It seems that unzipping the file using Windows explorer's zip support doesn't work properly. If you instead do as described in the README and run:
jar xvf glassfish-4.1.zip
The archive is extracted properly and all the needed pkg files are there.
What files do you need? I had the save problem I was looking for the files of tutorial. Finally I found them here: ..../glassfish4/docs/javaee-tutorial/

License error with Saiku Analytics Plugin on Pentaho 6 CE

I installed Saiku Analytics 3.8.7 on pentaho 6 CE using marketplace with COMMUNITY license, but when i try to use it show me: "Error creating session: License for wrong version please update your free license".
I try create different types of licenses in meteorite.bi with no luck. Also if I want to uninstall it using the marketplace throw me an error.
What I can do?
I had the same issue.
Saiku Analytics was not working and failed to uninstall without any error in catalina.out and pentaho.log.
To uninstalled plugin I had to call biserver-ce/pentaho-solutions/system/marketplace/processes/uninstall_plugin.kjb kettle job.
It has 3 params:
samplesDir - set it to empty string.
uninstallBackup - (absolute path to folder where plugin backup will be stored) ex: /Users/taras/programs/biserver-ce/pentaho-solutions/system/plugin-cache/backups/saiku_backup.
uninstallLocation - (absolute path to folder where plugin is located) ex : /Users/taras/programs/biserver-ce/pentaho-solutions/system/plugins/saiku .
Job can be executed using Spoon.
After it I've restarted PUC and installed plugin one more time. I selected plugin version '3.8.8 (PENTAHO6)' version from dropdown. Then I followed instructions from popup and downloaded saiku-olap-util-3.7-SNAPSHOT.jar to tomcat/webapps/pentaho/WEB-INF/lib/ folder and generated licence on licensing.meteorite.bi (License Type: COMMUNITY_EDITION) and downloaded it into /Users/taras/programs/biserver-ce/pentaho-solutions/system/plugins/saiku folder. After PUC restart saiku started to work.
Actually I'm disappointed - PUC 6 is so unstable...not sure if its a good production ready solution :(
I had the exact same issue. Turns out in the pentaho marketplace, I had wrongly downloaded the Enterprise version of the plugin, and not the Community edition (they're both under Saiku Analytics plugin entry, but there's a dropdown once you select the plugin that lets you choose the right version).
You need to delete the appendix of the license data you got.
When your license looks like license_localhost.lic you need to rename it to license.lic.
And save to the right location like that: ..\pentaho-solutions\system\saiku
Copy the license file into following path: ./tomcat/webapps/pentaho/WEB-INF/lib/license.lic
to resolve this Issue
Just try to download Saiku 3.8.8(STABLE) from Marketplace & you can able to apply license for 20 users also..

Application cannot be imported; it is either an invalid one or it contains specific features that are not supported

I followed the recommended solution:
IBM Worklight v6.0 - Error while adding an application to the Mobile Test Workbench
still got the error even though my jdk seems to be already correct
I didn't see any errors in the test workbench mobile client log (emulator), which log should I be looking at?
I suppose that you are using Android 4.4 and not Android 4.4W or 4.4L which are not yet supported. And you should have made recently an update of the Android SDK tools to version 23 (you can verify by opening the SDK Manager)
Google has modified in this release the way the tools are organized and this made MTWW regressed when instrumenting.
There is a workaround: copy <android-sdk-dir>/build-tools/20.0.0/zipalign[.exe] to <android-sdk-dir>/tools.
Dominique
I had same problem. You may need hotfix or uptdate to RTW8.6.
https://www-304.ibm.com/support/docview.wss?uid=swg21678859